From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] dt-bindings: regulator: mt6359: make regulator names unique
Date: Fri, 20 Feb 2026 08:51:33 +0100 [thread overview]
Message-ID: <20260220-bizarre-tricky-stingray-94db2b@quoll> (raw)
In-Reply-To: <20260219-mtk-mt6359-fix-regulator-names-v1-2-ee0fcebfe1d9@baylibre.com>
On Thu, Feb 19, 2026 at 04:55:30PM -0600, David Lechner wrote:
> Update the example devicetree with unique regulator names for all
> regulators. This reflects the same change made to the actual .dtsi file.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
Subject: regulator
> Documentation/devicetree/bindings/regulator/mt6359-regulator.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-20 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 22:55 [PATCH 0/2] arm64: dts: mediatek: mt6359: give regulators unique names David Lechner
2026-02-19 22:55 ` [PATCH 1/2] " David Lechner
2026-02-23 13:44 ` AngeloGioacchino Del Regno
2026-02-19 22:55 ` [PATCH 2/2] dt-bindings: regulator: mt6359: make regulator names unique David Lechner
2026-02-20 7:51 ` Krzysztof Kozlowski [this message]
2026-02-23 14:46 ` (subset) [PATCH 0/2] arm64: dts: mediatek: mt6359: give regulators unique names Mark Brown
2026-02-24 9:34 ` AngeloGioacchino Del Regno
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=20260220-bizarre-tricky-stingray-94db2b@quoll \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@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