diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-09-23 19:12:18 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-09-23 19:12:18 +0300 |
| commit | 1707c39ae309bf91965aa6f04d63816a090d90a1 (patch) | |
| tree | 1cb7ccf1c39de48dfda9ff205b27f8bb704c80e6 /arch | |
| parent | 33a4e37ebc8ccdfe2c51306b1a40d9e7d17b4691 (diff) | |
| parent | d7f06bdd6ee87fbefa05af5f57361d85e7715b11 (diff) | |
| download | linux-1707c39ae309bf91965aa6f04d63816a090d90a1.tar.xz | |
Merge tag 'driver-core-6.0-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
Pull driver core fixes from Greg KH:
"Here are two tiny driver core fixes for 6.0-rc7 that resolve some
oft-reported problems.
The first is a revert of the "fw_devlink.strict=1" default option that
we keep trying to enable, but we keep finding platforms that this just
breaks everything on. So again, we need it reverted and hopefully it
can be worked on in future releases.
The second is a sysfs file-size bugfix that resolves an issue that
many people are starting to hit as the fix it is fixing also was
backported to stable kernels. The util-linux developers are starting
to get bugreports about sysfs files that contain no data because of
this problem, and this fix which has been in linux-next in the
bitfield tree for a long time, resolves it. I'm submitting it here as
it needs to be merged for 6.0-final, not for 6.1-rc1.
Both of these have been in linux-next with no reported issues, only
reports were that these fixed problems"
* tag 'driver-core-6.0-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES
Revert "driver core: Set fw_devlink.strict=1 by default"
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions