From: Mark Brown <broonie@kernel.org>
To: Jim Wylder <jwylder@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: Account for register length when chunking
Date: Fri, 19 May 2023 02:31:12 +0900 [thread overview]
Message-ID: <168443107216.480556.12280205564293032202.b4-ty@kernel.org> (raw)
In-Reply-To: <20230517152444.3690870-2-jwylder@google.com>
On Wed, 17 May 2023 10:20:11 -0500, Jim Wylder wrote:
> Currently, when regmap_raw_write() splits the data, it uses the
> max_raw_write value defined for the bus. For any bus that includes
> the target register address in the max_raw_write value, the chunked
> transmission will always exceed the maximum transmission length.
> To avoid this problem, subtract the length of the register and the
> padding from the maximum transmission.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/1] regmap: Account for register length when chunking
commit: 3981514180c987a79ea98f0ae06a7cbf58a9ac0f
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-05-18 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:39 Jim Wylder
2023-05-15 14:59 ` Mark Brown
2023-05-16 15:52 ` Jim Wylder
2023-05-17 1:15 ` Mark Brown
2023-05-17 15:20 ` Jim Wylder
2023-05-17 15:20 ` [PATCH] " Jim Wylder
2023-05-18 17:31 ` Mark Brown [this message]
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=168443107216.480556.12280205564293032202.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwylder@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.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
all inboxes | Powered by JetHome®