From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Frieder Schrempf <frieder.schrempf@kontron.de>,
Joy Zou <joy.zou@nxp.com>,
ping.bai@nxp.com, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: regulator: pca9450: add pca9451a support
Date: Wed, 31 May 2023 11:11:40 +0200 [thread overview]
Message-ID: <0de8cecf-ec36-9300-656b-2c073f60c407@linaro.org> (raw)
In-Reply-To: <25e6d735-f191-68a1-84cc-d7e1ae4c3217@kontron.de>
On 31/05/2023 09:22, Frieder Schrempf wrote:
> On 31.05.23 08:56, Krzysztof Kozlowski wrote:
>> On 31/05/2023 08:57, Joy Zou wrote:
>>> Update pca9450 bindings.
>>>
>>> Signed-off-by: Joy Zou <joy.zou@nxp.com>
>>> ---
>>
>> Subject prefix is: regulator: dt-bindings: pca9450:
>
> Is there some way to have this consistent for all subsystems? Most
> subsystems seem to use:
>
> dt-bindings: [subsystem]:
>
> But some use:
>
> [subsystem]: dt-bindings:
>
> Casual contributors (like me) will very often get it wrong on the first
> try. Examining the history is extra effort that could be avoided and
> often doesn't provide a definite hint as you find both variations in the
> past.
>
> Can we standardize this and make checkpatch validate the subject line?
I understand your pain. :)
My expectation is just to have "dt-bindings:" prefix. It can be anywhere
- first or second, doesn't matter to me.
Then there is the generic rule that subsystem prefix should be the first
and here there is a disagreement between some folks. Most maintainers
either don't care or assume bindings are separate subsystem. Mark (spi,
ASoC, regulator) and media-folks say it is not separate subsystem (real
subsystem are spi, regulator etc), thus they want their subsystem name
as the first prefix. It sounds reasonable. Anyway it does not contradict
DT bindings maintainers expectation to have somewhere "dt-bindings:" prefix.
My comment was only to help you and there is no need to resend. I think
Mark when applying will drop "dt-bindings" prefix if is before
regulator, though. Life, no big deal.
Whether checkpatch can do this? Sure, quite likely, one just need some
Perl-foo to add such rule. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-31 9:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 6:57 [PATCH v1 0/3] add pmic pca9451a support Joy Zou
2023-05-31 6:57 ` [PATCH v1 1/3] dt-bindings: regulator: pca9450: add " Joy Zou
2023-05-31 6:56 ` Krzysztof Kozlowski
2023-05-31 7:00 ` [EXT] " Joy Zou
2023-05-31 7:22 ` Frieder Schrempf
2023-05-31 9:11 ` Krzysztof Kozlowski [this message]
2023-05-31 9:20 ` Frieder Schrempf
2023-05-31 10:41 ` [EXT] " Joy Zou
2023-05-31 6:57 ` [PATCH v1 2/3] " Joy Zou
2023-05-31 11:34 ` Alexander Stein
2023-07-05 6:50 ` [EXT] " Joy Zou
2023-07-05 13:12 ` Alexander Stein
2023-07-17 9:53 ` [EXT] " Joy Zou
2023-07-17 13:33 ` Mark Brown
2023-08-01 10:17 ` Joy Zou
[not found] ` <AM6PR04MB59255766CED30160FB552F94E10AA@AM6PR04MB5925.eurprd04.prod.outlook.com>
2023-10-17 14:02 ` Alexander Stein
2023-10-19 7:47 ` [EXT] " Joy Zou
2023-05-31 6:57 ` [PATCH v1 3/3] arm64: dts: imx93-11x11-evk: " Joy Zou
2023-05-31 11:18 ` Mark Brown
2023-08-01 10:17 ` [EXT] " Joy Zou
2024-03-25 17:44 ` (subset) [PATCH v1 0/3] add pmic " 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=0de8cecf-ec36-9300-656b-2c073f60c407@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=joy.zou@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).