From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qianhui Xu <xiaqinghuan@mail.ustc.edu.cn>,
Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: regulator: add Will Semiconductor WL2868C PMIC
Date: Wed, 28 Oct 2026 13:12:29 +0100 [thread overview]
Message-ID: <0f60fcba-8f31-4b3d-a7d8-8dee548e0b41@kernel.org> (raw)
In-Reply-To: <20261028120432.99230-1-xiaqinghuan@mail.ustc.edu.cn>
On 28/10/2026 13:04, Qianhui Xu wrote:
> On Tue, Oct 27, 2026 at 05:58:24PM +0000, Mark Brown wrote:
>> Please submit patches using subject lines reflecting the style for the
>> subsystem, this makes it easier for people to identify relevant patches.
>
> Changed in v2 to:
>
> regulator: dt-bindings: willsemi,wl2868c: add the WL2868C camera PMIC
>
> which is the shape the regulator tree is using (e.g. "regulator:
> dt-bindings: ti,lp872x: Document input supplies", "regulator:
> dt-bindings: sy8827n: support standard properties"). The v1 prefix was
> copied from the media-side bindings I was preparing in the same batch,
> which was my mistake.
>
>>> +WILLSEMI WL2868C CAMERA PMIC DRIVER
>>
>> Please keep the file sorted.
>
> Moved. It was sitting after "VOLTAGE AND CURRENT REGULATOR FRAMEWORK",
> which is the V section, while the entry name starts with W. It is now
> between "WIIMOTE HID DRIVER" and "WILOCITY WIL6210 WIRELESS DRIVER".
>
That's LLM output. Why do you paste it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-28 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 5:10 Qianhui Xu
2026-10-27 17:58 ` Mark Brown
2026-10-28 12:04 ` Qianhui Xu
2026-10-28 12:12 ` Krzysztof Kozlowski [this message]
2026-10-27 18:04 ` Krzysztof Kozlowski
2026-10-28 12:04 ` Qianhui Xu
2026-10-28 12:11 ` Krzysztof Kozlowski
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=0f60fcba-8f31-4b3d-a7d8-8dee548e0b41@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xiaqinghuan@mail.ustc.edu.cn \
/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®