From: Lee Jones <lee@kernel.org>
To: Lee Jones <lee@kernel.org>, Nishanth Menon <nm@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-stm32@st-md-mailman.stormreply.com,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Subject: Re: (subset) [PATCH V2] mfd: syscon: Use regmap max_register_is_0 as needed
Date: Mon, 30 Sep 2024 15:43:43 +0100 [thread overview]
Message-ID: <172770742318.523866.16912261914335612487.b4-ty@kernel.org> (raw)
In-Reply-To: <20240903184710.1552067-1-nm@ti.com>
On Tue, 03 Sep 2024 13:47:10 -0500, Nishanth Menon wrote:
> syscon has always set the optional max_register configuration of
> regmap to ensure the correct checks are in place. However, a recent
> commit 0ec74ad3c157 ("regmap: rework ->max_register handling")
> introduced explicit configuration in regmap framework for register
> maps that is exactly 1 register, when max_register is pointing to a
> valid register 0. This commit solved a previous limitation of regmap
> framework.
>
> [...]
Applied, thanks!
[1/1] mfd: syscon: Use regmap max_register_is_0 as needed
commit: bf5b2ddf06da57fa623c11d599697a98f1007752
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-09-30 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 18:47 Nishanth Menon
2024-09-27 12:00 ` Nishanth Menon
2024-09-30 14:43 ` Lee Jones [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=172770742318.523866.16912261914335612487.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=nm@ti.com \
--cc=shawnguo@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®