From: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] regulator: consumer.rst: document bulk operations
Date: Wed, 20 Aug 2025 21:59:05 +0800 [thread overview]
Message-ID: <DC7B4DGBA8RK.14Y0UOAKOEOWD@gmail.com> (raw)
In-Reply-To: <dc1107f3-098d-4952-8133-9bd6068d1100@sirena.org.uk>
On Tue Aug 19, 2025 at 11:52 PM CST, Mark Brown wrote:
> On Tue, Aug 19, 2025 at 12:25:43PM +0800, Javier Carrasco wrote:
>> The current consumer documentation does not include bulk operations,
>> providing an example of how to acquire multiple regulators by calling
>> regulator_get() multiple times. That solution is valid and slightly
>> simpler for a small amount of regulators, but it does not scale well.
>>
>> Document the bulk operations to get, enable and disable regulators.
>>
>> ---
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
>> ---
>
> You need to put the signoff before the ---, anything after the --- will
> get deleted when applying.
Sorry about that, I wrote a cover letter that I later removed, and b4
ended up adding the ---, which I missed before sending upstream.
Thank you for applying the patch, I am planning to update the
documentation of the regulator API when I have some time, and I will
make sure that the patches are properly formatted.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2025-08-20 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 4:25 Javier Carrasco
2025-08-19 15:52 ` Mark Brown
2025-08-20 13:59 ` Javier Carrasco [this message]
2025-08-19 19:47 ` 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=DC7B4DGBA8RK.14Y0UOAKOEOWD@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=broonie@kernel.org \
--cc=lenb@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@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®