From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Chao Wei <chao.wei@sophgo.com>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: riscv: add Milk-V Duo S board compatibles
Date: Mon, 22 Apr 2024 10:49:28 +0300 [thread overview]
Message-ID: <47a25b01-b087-4a3d-9af9-07bb58c8d5b8@collabora.com> (raw)
In-Reply-To: <505a8cea-5b0e-4ecf-b566-e68b37b2d4ed@bootlin.com>
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@bootlin.com wrote:
>>>>> From: Michael Opdenacker <michael.opdenacker@bootlin.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@bootlin.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-22 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 5:57 [PATCH v6 0/2] add initial Milk-V Duo S board support michael.opdenacker
2024-04-21 5:57 ` [PATCH v6 1/2] dt-bindings: riscv: add Milk-V Duo S board compatibles michael.opdenacker
2024-04-21 14:12 ` Krzysztof Kozlowski
2024-04-21 18:55 ` Michael Opdenacker
2024-04-22 4:24 ` Krzysztof Kozlowski
2024-04-22 6:23 ` Michael Opdenacker
2024-04-22 7:49 ` Cristian Ciocaltea [this message]
2024-04-21 5:57 ` [PATCH v6 2/2] riscv: dts: sophgo: add initial Milk-V Duo S board support michael.opdenacker
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=47a25b01-b087-4a3d-9af9-07bb58c8d5b8@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.opdenacker@bootlin.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=unicorn_wang@outlook.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).