[GIT PULL] Driver core fixes for 6.0-rc7

[Greg KH <gregkh@linuxfoundation.org>]

The following changes since commit 80e78fcce86de0288793a0ef0f6acf37656ee4cf:

  Linux 6.0-rc5 (2022-09-11 16:22:01 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.0-rc7

for you to fetch changes up to d7f06bdd6ee87fbefa05af5f57361d85e7715b11:

  drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES (2022-09-22 13:13:12 +0200)

----------------------------------------------------------------
Driver core fixes for 6.0-rc7

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.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      Revert "driver core: Set fw_devlink.strict=1 by default"

Phil Auld (1):
      drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES

 drivers/base/core.c     | 2 +-
 include/linux/cpumask.h | 5 +++--
 2 files changed, 4 insertions(+), 3 deletions(-)