From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robin Gong <yibin.gong@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 0/2] regulator: pca9450: add input supply links
Date: Tue, 28 Oct 2025 12:16:26 +0000 [thread overview]
Message-ID: <176165378617.53238.7226737509811324588.b4-ty@kernel.org> (raw)
In-Reply-To: <20251027124415.989301-1-o.rempel@pengutronix.de>
On Mon, 27 Oct 2025 13:44:13 +0100, Oleksij Rempel wrote:
> This series adds input supply definitions for the NXP PCA9450 PMIC.
>
> Some systems detect power events such as undervoltage before the PMIC.
> To allow correct propagation of such events, each regulator must define
> its upstream input supply. The first patch updates the devicetree
> binding to document new *-supply properties, and the second patch adds
> matching .supply_name entries in the driver.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] dt-bindings: regulator: nxp,pca9450: document input supplies
commit: 86df0030b71d7172317d957df17524a7fd6232d4
[2/2] regulator: pca9450: link regulator inputs to supply groups
commit: 4c33cef58965eb655a0ac8e243aa323581ec025f
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:[~2025-10-28 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 12:44 Oleksij Rempel
2025-10-27 12:44 ` [PATCH v1 1/2] dt-bindings: regulator: nxp,pca9450: document input supplies Oleksij Rempel
2025-10-28 19:31 ` Conor Dooley
2025-10-27 12:44 ` [PATCH v1 2/2] regulator: pca9450: link regulator inputs to supply groups Oleksij Rempel
2025-10-28 12:16 ` 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=176165378617.53238.7226737509811324588.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=yibin.gong@nxp.com \
/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®