public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regmap fixes for v6.4-rc7
Date: Wed, 21 Jun 2023 14:20:16 +0100	[thread overview]
Message-ID: <20230621132028.E6428C433C0@smtp.kernel.org> (raw)

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(-)

             reply	other threads:[~2023-06-21 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 13:20 Mark Brown [this message]
2023-06-21 17:39 ` [GIT PULL] regmap fixes for v6.4-rc7 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230621132028.E6428C433C0@smtp.kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox