linux-kernel - Re: [PATCH v6 1/2] dt-bindings: riscv: add Milk-V Duo S board compatibles

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] [day] [month] [year] [list]

Message-ID: <47a25b01-b087-4a3d-9af9-07bb58c8d5b8@collabora.com>
Date: Mon, 22 Apr 2024 10:49:28 +0300
From: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
To: Michael Opdenacker <michael.opdenacker@...tlin.com>,
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 Conor Dooley <conor@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Chen Wang <unicorn_wang@...look.com>, Inochi Amaoto <inochiama@...look.com>,
 Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
 <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
 Chao Wei <chao.wei@...hgo.com>
Cc: linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: riscv: add Milk-V Duo S board
 compatibles

Hi Michael,

On 4/22/24 9:23 AM, Michael Opdenacker wrote:
> 
> On 4/22/24 at 06:24, Krzysztof Kozlowski wrote:
>> On 21/04/2024 20:55, Michael Opdenacker wrote:
>>> Hi Krzysztof
>>>
>>> On 4/21/24 at 16:12, Krzysztof Kozlowski wrote:
>>>> On 21/04/2024 07:57, michael.opdenacker@...tlin.com wrote:
>>>>> From: Michael Opdenacker <michael.opdenacker@...tlin.com>
>>>>>
>>>>> Document the compatible strings for the Milk-V Duo S board[1] which
>>>>> uses
>>>>> the SOPHGO SG2000 SoC, compatible with the CV1812H SoC[2].
>>>>>
>>>>> Link: https://milkv.io/duo-s [1]
>>>>> Link: https://en.sophgo.com/product/introduce/cv181xH.html [2]
>>>>>
>>>>> Signed-off-by: Michael Opdenacker <michael.opdenacker@...tlin.com>
>>>>> ---
>>>> Where is the changelog? It's v6!
>>> Oops, it was in my cover letter
>>> (https://lore.kernel.org/linux-riscv/20240421055710.143617-1-michael.opdenacker@bootlin.com/T/#t),
>>> which you didn't get because of get-maintainer.pl. As the recipients are
>>> patch dependent, am I supposed to describe the changes in all patches
>>> and not only in the cover letter?
>> If you do not send the changelog to everyone, then yes, please describe
>> respective changes in each patch.
> 
> Ok, will do, thanks!
> 
>>
>> It's your choice, but if you decide not to send cover letter to some
>> folks, then *it does not exist* for such folks.
> 
> Well, actually, I shouldn't have let get-maintainer.pl decide for me. Is
> there a way to send the cover-letter to the union of people who will
> receive the individual patches?

You may call get-maintainer.pl once for all the patches in the series
(e.g. use a glob pattern to select all needed files) and then manually
edit the cover letter to provide the 'To:' and 'Cc:' fields.

Additionally, you could use '--to-cover --cc-cover' arguments passed to
'git send-email' so that all those recipients will receive all patches.

Alternatively, you may try the b4 utility [1], which is able to automate
most of the manual steps.

Hope this helps!

Regards,
Cristian

[1]: https://b4.docs.kernel.org/en/latest/contributor/prep.html