linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-rtc@vger.kernel.org, Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH v5 07/16] mfd: rohm-bd71828: Use regmap_reg_range()
Date: Wed, 26 Nov 2025 14:33:04 +0000	[thread overview]
Message-ID: <20251126143304.GE3070764@google.com> (raw)
In-Reply-To: <b0c6256deb1388f0774b3c855c0614d363aa003b.1763625920.git.mazziesaccount@gmail.com>

On Thu, 20 Nov 2025, Matti Vaittinen wrote:

> From: Matti Vaittinen <mazziesaccount@gmail.com>
> 
> The regmap range tables tend to be somewhat verbose. Using the
> regmap_reg_range() can make the definitions slightly mode compact.
> 
> Tidy the regmap range tables by using the regmap_reg_range().
> 
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> ---
> Revision history:
>  v2 => :
>  - no changes
>  RFCv1 => v2:
>  - New patch
> ---
>  drivers/mfd/rohm-bd71828.c | 64 +++++++++++---------------------------
>  1 file changed, 18 insertions(+), 46 deletions(-)

LGTM.

Once everything is in order, I plan to merge the set through MFD.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-11-26 14:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  8:19 [PATCH v5 00/16] Support ROHM BD72720 PMIC Matti Vaittinen
2025-11-20  8:19 ` [PATCH v5 01/16] dt-bindings: regulator: ROHM BD72720 Matti Vaittinen
2025-11-20  9:57   ` Rob Herring (Arm)
2025-11-20  8:19 ` [PATCH v5 02/16] dt-bindings: battery: Clarify trickle-charge Matti Vaittinen
2025-11-20  8:20 ` [PATCH v5 03/16] dt-bindings: battery: Add trickle-charge upper limit Matti Vaittinen
2025-11-20  8:20 ` [PATCH v5 04/16] dt-bindings: battery: Voltage drop properties Matti Vaittinen
2025-11-20 16:11   ` Rob Herring (Arm)
2025-11-20  8:20 ` [PATCH v5 05/16] dt-bindings: mfd: ROHM BD72720 Matti Vaittinen
2025-11-20  8:20 ` [PATCH v5 06/16] dt-bindings: leds: bd72720: Add BD72720 Matti Vaittinen
2025-11-20  8:21 ` [PATCH v5 07/16] mfd: rohm-bd71828: Use regmap_reg_range() Matti Vaittinen
2025-11-26 14:33   ` Lee Jones [this message]
2025-11-20  8:22 ` [PATCH v5 08/16] mfd: bd71828: Support ROHM BD72720 Matti Vaittinen
2025-11-26 14:28   ` Lee Jones
2025-11-27  7:46     ` Matti Vaittinen
2025-11-20  8:23 ` [PATCH v5 09/16] regulator: bd71828: rename IC specific entities Matti Vaittinen
2025-11-20  8:23 ` [PATCH v5 10/16] regulator: bd71828: Support ROHM BD72720 Matti Vaittinen
2025-11-20  8:23 ` [PATCH v5 11/16] gpio: Support ROHM BD72720 gpios Matti Vaittinen
2025-11-20  8:23 ` [PATCH v5 12/16] clk: clk-bd718x7: Support BD72720 clk gate Matti Vaittinen
2025-11-20  8:23 ` [PATCH v5 13/16] rtc: bd70528: Support BD72720 rtc Matti Vaittinen
2025-11-20  8:24 ` [PATCH v5 14/16] power: supply: bd71828: Support wider register addresses Matti Vaittinen
2025-11-20  8:24 ` [PATCH v5 15/16] power: supply: bd71828-power: Support ROHM BD72720 Matti Vaittinen
2025-11-20  8:24 ` [PATCH v5 16/16] MAINTAINERS: Add ROHM BD72720 PMIC Matti Vaittinen

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=20251126143304.GE3070764@google.com \
    --to=lee@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@kemnade.info \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=pavel@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sre@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;
as well as URLs for NNTP newsgroup(s).