From: "Paul Louvel" <paul.louvel@bootlin.com>
To: "Mark Brown" <broonie@kernel.org>,
"Paul Louvel" <paul.louvel@bootlin.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v5 3/3] regulator: Add TI LM51772 support
Date: Fri, 06 Nov 2026 17:44:42 +0100 [thread overview]
Message-ID: <DMOA2IJB4L56.1AIE3BMYG9QJJ@bootlin.com> (raw)
In-Reply-To: <ba06d540-e971-4e18-99d0-16f8f4530eb7@sirena.org.uk>
Hi Mark,
On Fri Nov 6, 2026 at 1:22 PM CET, Mark Brown wrote:
> On Fri, Nov 06, 2026 at 12:17:40PM +0100, Paul Louvel wrote:
>> On Fri Nov 6, 2026 at 11:12 AM CET, Paul Louvel wrote:
>> > Add driver for the TI LM51772 buck-boost voltage regulator.
>
> Please delete unneeded context from mails when replying. Doing this
> makes it much easier to find your reply in the message, helping ensure
> it won't be missed by people scrolling through the irrelevant quoted
> material.
Sure, thanks for the feedback.
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-11-06 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 10:12 [PATCH v5 0/3] Add TI LM51772 buck-boost voltage regulator Paul Louvel
2026-11-06 10:12 ` [PATCH v5 1/3] regulator: dt-bindings: Add TI LM51772 support Paul Louvel
2026-11-06 10:12 ` [PATCH v5 2/3] regulator: core: Support regulators where the voltage selector spans two registers Paul Louvel
2026-11-06 10:12 ` [PATCH v5 3/3] regulator: Add TI LM51772 support Paul Louvel
2026-11-06 11:17 ` Paul Louvel
2026-11-06 12:22 ` Mark Brown
2026-11-06 16:44 ` Paul Louvel [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=DMOA2IJB4L56.1AIE3BMYG9QJJ@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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®