linux-kernel - Re: [PATCH v3 1/4] dt-bindings: pinctrl: spacemit: add support for K1 SoC

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]

Message-ID: <eff3f5c5-3a25-498e-80da-ad8e039f7575@kernel.org>
Date: Mon, 2 Sep 2024 10:03:31 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Conor Dooley <conor.dooley@...rochip.com>,
 Chen Wang <unicorn_wang@...look.com>
Cc: Yixun Lan <dlan@...too.org>, Linus Walleij <linus.walleij@...aro.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Paul Walmsley
 <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
 Albert Ou <aou@...s.berkeley.edu>, Conor Dooley <conor@...nel.org>,
 devicetree@...r.kernel.org, Meng Zhang <zhangmeng.kevin@...cemit.com>,
 linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
 Jesse Taube <jesse@...osinc.com>, Yangyu Chen <cyy@...self.name>,
 Inochi Amaoto <inochiama@...look.com>, Jisheng Zhang <jszhang@...nel.org>,
 Meng Zhang <kevin.z.m@...mail.com>, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v3 1/4] dt-bindings: pinctrl: spacemit: add support for K1
 SoC

On 30/08/2024 09:06, Conor Dooley wrote:
> On Fri, Aug 30, 2024 at 07:48:17AM +0800, Chen Wang wrote:
>>
>> On 2024/8/28 19:30, Yixun Lan wrote:
>>> Add dt-bindings for the pinctrl driver of SpacemiT's K1 SoC.
>>>
>>> Signed-off-by: Yixun Lan <dlan@...too.org>
>>> ---
>>> Changes in v3:
>>> - drop spacemit,slew-rate-{enable,disable} property
>>> - use drive-strength instead of drive-strength-microamp
>>> - fold strong-pull-up into bias-pull-up
>>> - format fixed
>>> - title fixed
>>
>> Drop this change history here, you can add this in the cover letter.
>>
>> [......]
> 
> It's perfectly fine to provide per-patch changelogs fyi, rather than in
> the cover letter.
> 

And honestly, since some time I prefer it much more. Much, much easier
to spot which patch changed instead of something in cover letter like:
1. Patch #1: changed foo
2. Patch #3: dropped
3. Patch #4 (so patch #5 or #4?): changed bar


Best regards,
Krzysztof