From: Mark Brown <broonie@kernel.org>
To: Artur Weber <aweber.kernel@gmail.com>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Stanislav Jakubek <stano.jakubek@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v9 7/8] regulator: bcm590xx: Rename BCM59056-specific data as such
Date: Fri, 16 May 2025 14:31:14 +0200 [thread overview]
Message-ID: <aCcwEtpjpEv_FiKB@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20250515-bcm59054-v9-7-14ba0ea2ea5b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
On Thu, May 15, 2025 at 04:16:34PM +0200, Artur Weber wrote:
> Previously, the driver used the BCM590XX prefix for register data
> specific to the BCM59056. As we will be introducing other regulators
> to this driver as well, make the BCM59056-specific values use the
> BCM59056 prefix.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-16 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 14:16 [PATCH v9 0/8] mfd: bcm590xx: Add support for BCM59054 Artur Weber
2025-05-15 14:16 ` [PATCH v9 1/8] dt-bindings: mfd: brcm,bcm59056: Convert to YAML Artur Weber
2025-05-15 14:16 ` [PATCH v9 2/8] dt-bindings: mfd: brcm,bcm59056: Add compatible for BCM59054 Artur Weber
2025-05-15 14:16 ` [PATCH v9 3/8] mfd: bcm590xx: Add support for multiple device types + BCM59054 compatible Artur Weber
2025-05-15 14:16 ` [PATCH v9 4/8] mfd: bcm590xx: Add PMU ID/revision parsing function Artur Weber
2025-05-15 14:16 ` [PATCH v9 5/8] regulator: bcm590xx: Use dev_err_probe for regulator register error Artur Weber
2025-05-16 11:56 ` Mark Brown
2025-05-15 14:16 ` [PATCH v9 6/8] regulator: bcm590xx: Store regulator descriptions in table Artur Weber
2025-05-16 12:30 ` Mark Brown
2025-05-15 14:16 ` [PATCH v9 7/8] regulator: bcm590xx: Rename BCM59056-specific data as such Artur Weber
2025-05-16 12:31 ` Mark Brown [this message]
2025-05-15 14:16 ` [PATCH v9 8/8] regulator: bcm590xx: Add support for BCM59054 regulators Artur Weber
2025-05-16 12:32 ` Mark Brown
2025-05-22 10:05 ` [PATCH v9 0/8] mfd: bcm590xx: Add support for BCM59054 Lee Jones
2025-05-22 14:45 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window Lee Jones
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=aCcwEtpjpEv_FiKB@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=aweber.kernel@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®