From: Dragan Simic <dsimic@manjaro.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Maximilian Weigand <mweigand@mweigand.net>,
Marek Kraus <gamiee@pine64.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: rockchip: add 'chassis-type' property on PineNote
Date: Fri, 07 Feb 2025 18:12:10 +0100 [thread overview]
Message-ID: <97df4fc0db4bf43a2a3f2d4d110e3105@manjaro.org> (raw)
In-Reply-To: <D7MD194WS7UL.FT324IUB9BIA@cknow.org>
On 2025-02-07 17:39, Diederik de Haas wrote:
> On Fri Feb 7, 2025 at 4:01 PM CET, Dragan Simic wrote:
>> On 2025-02-07 12:11, Diederik de Haas wrote:
>>> Add the recommended chassis-type root node property so userspace can
>>> request the form factor and adjust their behavior accordingly.
>>>
>>> Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
>>> Link:
>>> https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter3-devicenodes.rst#root-node
>>
>> Maybe the Link tag should be converted into a "[1]" reference?
>> To me, this is more like a reference for this DT addition.
>>
>> In general, references can also be placed closer to the contents
>> they back up, which isn't possible with Link tags, but of course
>> that doesn't matter much in this case.
>
> I generally use the "[1]" format when linking to specific claims, which
> I could've done wrt the "recommended". But I considered this a general
> background link and then I prefer to do it via a Link tag.
>
> If requested by a maintainer I'll change it ofc, but otherwise I prefer
> to keep it as is.
Indeed, in this case it's pretty much irrelevant which format is used.
In fact, it may look nicer to use a Link tag, because there are only
a few lines in the patch description in total. :)
My comment was more about longer commit/patch descriptions with multiple
references, which should benefit from placing references closer to the
backed-up contents using the "[*]" layout, instead of relying on Link
tags to bunch it all together at the end of the description.
next prev parent reply other threads:[~2025-02-07 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 11:11 [PATCH v1] arm64: dts: rockchip: add 'chassis-type' property on PineNote Diederik de Haas
2025-02-07 15:01 ` Dragan Simic
2025-02-07 16:39 ` Diederik de Haas
2025-02-07 17:12 ` Dragan Simic [this message]
2025-02-10 10:39 ` Heiko Stuebner
2025-02-10 11:06 ` Krzysztof Kozlowski
2025-02-10 12:06 ` Heiko Stübner
2025-02-10 12:47 ` Diederik de Haas
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=97df4fc0db4bf43a2a3f2d4d110e3105@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=gamiee@pine64.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mweigand@mweigand.net \
--cc=robh@kernel.org \
/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).