From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: dri-devel@lists.freedesktop.org,
"Johan Hovold" <johan+linaro@kernel.org>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, "Daniel Vetter" <daniel@ffwll.ch>,
linux-amlogic@lists.infradead.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Miaoqian Lin" <linmq006@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Alexandru Tachici" <alexandru.tachici@analog.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Guenter Roeck" <linux@roeck-us.net>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Stephen Boyd" <sboyd@kernel.org>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Alexandru Ardelean" <aardelean@deviqon.com>,
linux-hwmon@vger.kernel.org, linux-clk@vger.kernel.org,
"Nuno Sá" <nuno.sa@analog.com>,
"Robert Foss" <robert.foss@linaro.org>,
"Aswath Govindraju" <a-govindraju@ti.com>,
"David Airlie" <airlied@linux.ie>,
linux-iio@vger.kernel.org
Subject: Re: (subset) [PATCH v2 0/7] Devm helpers for regulator get and enable
Date: Thu, 18 Aug 2022 14:33:53 +0300 [thread overview]
Message-ID: <52d307d7-04f2-89fd-ff4b-9a6c0d247350@gmail.com> (raw)
In-Reply-To: <166057828406.697572.228317501909350108.b4-ty@kernel.org>
Hi Mark,
On 8/15/22 18:44, Mark Brown wrote:
> 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!
>
> [1/7] docs: devres: regulator: Add missing devm_* functions to devres.rst
> commit: 9b6744f60b6b47bc0757a1955adb4d2c3ab22e13
> [2/7] regulator: Add devm helpers for get and enable
> (no commit info)
>
I was planning to send out the v3 (where IIO patches are no longer
squashed into one). I didn't spot the above mentioned patch 2/7 from
regulator/for-next. I'd just like to get confirmation the 2/7 was not
merged even though it's mentioned in this mail before re-spinning the
series with it.
Best Regards
--Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-08-18 11:34 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 [this message]
2022-08-18 11:54 ` Mark Brown
2022-08-18 12:04 ` Vaittinen, Matti
2022-08-18 14:01 ` Mark Brown
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=52d307d7-04f2-89fd-ff4b-9a6c0d247350@gmail.com \
--to=mazziesaccount@gmail.com \
--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=broonie@kernel.org \
--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=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).