From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: (subset) [PATCH v2 1/5] regulator: implement dev_of_regulator_get
Date: Wed, 29 Oct 2025 07:27:07 +0100 [thread overview]
Message-ID: <176171922719.3414186.16216046073392207449.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251027192938.2586566-1-a.fatoum@barebox.org>
On Mon, 27 Oct 2025 20:28:16 +0100, Ahmad Fatoum wrote:
> Regulators for a device need not be listed in the main node associated
> with a device. Export dev_of_regulator_get for these use cases to
> simplify porting Linux drivers.
>
>
Applied, thanks!
[1/5] regulator: implement dev_of_regulator_get
https://git.pengutronix.de/cgit/barebox/commit/?id=83ce8c39336d (link may not be stable)
[2/5] pmdomain: look up pmdomain even if not have_genpd_providers
https://git.pengutronix.de/cgit/barebox/commit/?id=abf97f3993e3 (link may not be stable)
[4/5] pmdomain: allow callback for when devices are attached
https://git.pengutronix.de/cgit/barebox/commit/?id=44c6bedbd439 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-10-29 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:28 Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 2/5] pmdomain: look up pmdomain even if not have_genpd_providers Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 3/5] pmdomain: warn if deep probe enabled and driver missing Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 4/5] pmdomain: allow callback for when devices are attached Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 5/5] pmdomain: add Rockchip power domain support Ahmad Fatoum
2025-10-28 8:57 ` Sascha Hauer
2025-10-28 9:04 ` Ahmad Fatoum
2025-10-28 9:48 ` Sascha Hauer
2025-10-28 10:41 ` Ahmad Fatoum
2025-10-28 10:46 ` Sascha Hauer
2025-10-28 11:01 ` Ahmad Fatoum
2025-10-29 6:27 ` Sascha Hauer [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=176171922719.3414186.16216046073392207449.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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