From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javierm@redhat.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Liam Girdwood <lgirdwood@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
Tejun Heo <tj@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Add option to prevent disabling unused regulators
Date: Mon, 13 Nov 2023 19:40:22 +0000 [thread overview]
Message-ID: <169990442285.3294075.7217773943260715696.b4-ty@kernel.org> (raw)
In-Reply-To: <20231028102423.179400-1-javierm@redhat.com>
On Sat, 28 Oct 2023 12:24:03 +0200, Javier Martinez Canillas wrote:
> This may be useful for debugging and develompent purposes, when there are
> drivers that depend on regulators to be enabled but do not request them.
>
> It is inspired from the clk_ignore_unused and pd_ignore_unused parameters,
> that are used to keep firmware-enabled clocks and power domains on even if
> these are not used by drivers.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: core: Add option to prevent disabling unused regulators
commit: c986968fe92f20f2db26fa6bce27795b2e9ebe22
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:[~2023-11-13 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 10:24 Javier Martinez Canillas
2023-10-28 16:04 ` Randy Dunlap
2023-10-30 14:53 ` Brian Masney
2023-11-01 4:56 ` Manivannan Sadhasivam
2023-11-01 13:09 ` Mark Brown
2023-11-02 9:33 ` Javier Martinez Canillas
2023-11-13 19:40 ` 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=169990442285.3294075.7217773943260715696.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=javierm@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=paulmck@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@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
all inboxes | Powered by JetHome®