From: Daniel Palmer <daniel@0x0f.com>
To: Romain Perier <romain.perier@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] ARM: mstar: Initial Miyoo Mini support
Date: Fri, 17 Dec 2021 01:18:17 +0900 [thread overview]
Message-ID: <CAFr9PX=AAssT1imCfpU_piGBOemD23RGBZzngznyia-4TXrK=g@mail.gmail.com> (raw)
In-Reply-To: <CABgxDoKJRc_qORcpFx=eNPS=bGV68hPrbeH0VtcQ2Jjx2ruqmg@mail.gmail.com>
Hi Romain,
On Fri, 17 Dec 2021 at 00:53, Romain Perier <romain.perier@gmail.com> wrote:
>
> Hi Daniel,
>
> Le jeu. 16 déc. 2021 à 11:52, Daniel Palmer <daniel@0x0f.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
next prev parent reply other threads:[~2021-12-16 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 10:52 [PATCH v2 0/3] ARM: mstar: Initial Miyoo Mini support Daniel Palmer
2021-12-16 10:52 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add prefix for Miyoo Daniel Palmer
2021-12-16 20:54 ` Rob Herring
2021-12-16 10:52 ` [PATCH v2 2/3] dt-bindings: arm: mstar: Add compatible for Miyoo Mini Daniel Palmer
2021-12-16 10:52 ` [PATCH v2 3/3] ARM: dts: mstar: Add a dts " Daniel Palmer
[not found] ` <CABgxDoKJRc_qORcpFx=eNPS=bGV68hPrbeH0VtcQ2Jjx2ruqmg@mail.gmail.com>
2021-12-16 16:18 ` Daniel Palmer [this message]
2021-12-16 17:34 ` [PATCH v2 0/3] ARM: mstar: Initial Miyoo Mini support Romain Perier
2021-12-16 17:48 ` Daniel Palmer
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='CAFr9PX=AAssT1imCfpU_piGBOemD23RGBZzngznyia-4TXrK=g@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=romain.perier@gmail.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 NNTP newsgroup(s).