linux-kernel - [GIT PULL] regmap fixes for v6.4-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230621132028.E6428C433C0@smtp.kernel.org>
Date:   Wed, 21 Jun 2023 14:20:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: [GIT PULL] regmap fixes for v6.4-rc7

The following changes since commit 44e46572f0bae431a6092e3cfd2f47bff8b8d18c:

  regmap: regcache: Don't sync read-only registers (2023-06-13 13:15:00 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v6.4-rc7

for you to fetch changes up to c8e796895e2310b6130e7577248da1d771431a77:

  regmap: spi-avmm: Fix regmap_bus max_raw_write (2023-06-20 21:31:08 +0100)

----------------------------------------------------------------
regmap: One more fix for v6.4

The earlier fix to take account of the register data size when limiting
raw register writes exposed the fact that the Intel AVMM bus was
incorrectly specifying too low a limit on the maximum data transfer, it
is only capable of transmitting one register so had set a transfer size
limit that couldn't fit both the value and the the register address into
a single message.

----------------------------------------------------------------
Russ Weight (1):
      regmap: spi-avmm: Fix regmap_bus max_raw_write

 drivers/base/regmap/regmap-spi-avmm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)