[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFr9PX=AAssT1imCfpU_piGBOemD23RGBZzngznyia-4TXrK=g@mail.gmail.com>
Date: Fri, 17 Dec 2021 01:18:17 +0900
From: Daniel Palmer <daniel@...f.com>
To: Romain Perier <romain.perier@...il.com>
Cc: devicetree <devicetree@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Rob Herring <robh+dt@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] ARM: mstar: Initial Miyoo Mini support
Hi Romain,
On Fri, 17 Dec 2021 at 00:53, Romain Perier <romain.perier@...il.com> wrote:
>
> Hi Daniel,
>
> Le jeu. 16 déc. 2021 à 11:52, Daniel Palmer <daniel@...f.com> a écrit :
>>
>> - I've left the link tags as-is as using them for linking
>> to background info seems acceptable.
>
>
> https://www.kernel.org/doc/html/latest/maintainer/configure-git.html#creating-commit-links-to-lore-kernel-org
The explanation of Link seem to have been updated recently in
1f57bd42b77cdc4b8e05ba9f4417872a6691b66d
(https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
a few paragraphs down).
My reading of the paragraph since that commit is: Explain what the
commit does in the commit message. If there is a bug that prompted the
change then link it. If there is some background for the commit then
link it.
If it needs to be changed around I'll do that but I personally think
it looks nicer. It seems like the right way to provide links to
datasheets etc without putting a bunch of long messy urls into the
commit message.
Cheers,
Daniel
Powered by blists - more mailing lists