[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b52685a3-127a-4367-b11a-54ab88467dcf@web.de>
Date: Sat, 25 May 2024 14:11:05 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Conor Dooley <conor@...nel.org>, Henry Bell <dmoo_dv@...tonmail.com>,
linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org
Cc: Albert Ou <aou@...s.berkeley.edu>, Conor Dooley <conor+dt@...nel.org>,
Emil Renner Berthing <kernel@...il.dk>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Palmer Dabbelt <palmer@...belt.com>, Paul Walmsley
<paul.walmsley@...ive.com>, Rob Herring <robh@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: RISC-V: add Star64 board devicetree
>>> Would you like to add an imperative wording for an improved change description?
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94
…
>> I'm happy to change it, but was going off the format used in Conor's Milkv Mars commit
>> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/commit/?id=04a228aadb84d894721b13197649ca741f3018bc
>
> Don't worry about Markus, most maintainers (myself included) ignore his
> comments on patches. The commit message here is fine.
Would such a response mean also that you are occasionally ignoring requirements
from a referenced Linux development guideline?
Regards,
Markus
Powered by blists - more mailing lists