lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 31 May 2023 09:22:45 +0200
From:   Frieder Schrempf <frieder.schrempf@...tron.de>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Joy Zou <joy.zou@....com>, ping.bai@....com,
        lgirdwood@...il.com, broonie@...nel.org, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
        shawnguo@...nel.org, s.hauer@...gutronix.de
Cc:     kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: regulator: pca9450: add pca9451a
 support

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@....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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ