From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Nuno Sá <nuno.sa@analog.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Miaoqian Lin <linmq006@gmail.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
Johan Hovold <johan+linaro@kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Alexandru Tachici <alexandru.tachici@analog.com>,
linux-doc@vger.kernel.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Jonas Karlman <jonas@kwiboo.se>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-iio@vger.kernel.org, Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jean Delvare <jdelvare@suse.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Aswath Govindraju <a-govindraju@ti.com>,
linux-amlogic@lists.infradead.org,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-clk@vger.kernel.org,
Alexandru Ardelean <aardelean@deviqon.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: Re: (subset) [PATCH v2 0/7] Devm helpers for regulator get and enable
Date: Thu, 18 Aug 2022 15:01:54 +0100 [thread overview]
Message-ID: <166083131403.91659.16911525815673537629.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1660292316.git.mazziesaccount@gmail.com>
On Fri, 12 Aug 2022 13:08:17 +0300, Matti Vaittinen wrote:
> Devm helpers for regulator get and enable
>
> First patch in the series is actually just a simple documentation fix
> which could be taken in as it is now.
>
> A few* drivers seem to use pattern demonstrated by pseudocode:
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[2/7] regulator: Add devm helpers for get and enable
commit: da279e6965b3838e99e5c0ab8f76b87bf86b31a5
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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-08-18 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 10:08 [PATCH v2 0/7] Devm helpers for regulator get and enable Matti Vaittinen
2022-08-12 10:11 ` [PATCH v2 5/7] gpu: drm: simplify drivers using devm_regulator_*get_enable*() Matti Vaittinen
2022-08-15 15:44 ` (subset) [PATCH v2 0/7] Devm helpers for regulator get and enable Mark Brown
2022-08-15 15:54 ` Laurent Pinchart
2022-08-15 16:33 ` Mark Brown
2022-08-15 18:52 ` Laurent Pinchart
2022-08-15 20:58 ` Stephen Boyd
2022-08-15 21:17 ` Laurent Pinchart
2022-08-15 22:55 ` Mark Brown
2022-08-16 4:56 ` Matti Vaittinen
2022-08-16 10:36 ` Mark Brown
2022-08-16 11:06 ` Vaittinen, Matti
2022-08-16 11:31 ` Mark Brown
2022-08-16 8:42 ` Andy Shevchenko
2022-08-15 22:07 ` Mark Brown
2022-08-30 19:42 ` Stephen Boyd
2022-08-16 8:23 ` Andy Shevchenko
2022-08-18 11:33 ` Matti Vaittinen
2022-08-18 11:54 ` Mark Brown
2022-08-18 12:04 ` Vaittinen, Matti
2022-08-18 14:01 ` 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=166083131403.91659.16911525815673537629.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Michael.Hennerich@analog.com \
--cc=a-govindraju@ti.com \
--cc=aardelean@deviqon.com \
--cc=airlied@linux.ie \
--cc=alexandru.tachici@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jdelvare@suse.com \
--cc=jernej.skrabec@gmail.com \
--cc=jic23@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=jonas@kwiboo.se \
--cc=khilman@baylibre.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linmq006@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo@kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=nuno.sa@analog.com \
--cc=robert.foss@linaro.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).