From: Francesco Dolcini <francesco@dolcini.it>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Martyn Welch <martyn.welch@collabora.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: Add device trees for MSC SM2S-IMX8PLUS SoM and carrier board
Date: Tue, 19 Jul 2022 12:15:46 +0200 [thread overview]
Message-ID: <YtaEUvP4jpO5Dggg@gaggiata.pivistrello.it> (raw)
In-Reply-To: <4473378f-1c14-3ec7-5380-12f49f3b1e3b@linaro.org>
Hello Krzysztof,
On Tue, Jul 19, 2022 at 12:01:34PM +0200, Krzysztof Kozlowski wrote:
> On 18/07/2022 17:23, Martyn Welch wrote:
> > + tca6424: gpio@22 {
> > + compatible = "ti,tca6424";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_tca6424>;
> > + reg = <0x22>;
>
> compatible, then reg, then all other properties. This applies everywhere.
Is this documented somewhere? It would be easier to enable new people to
contribute, if it was.
Anyway, I would add to this list status as last, when present, and I do
try to order alphabetically all the other properties.
Francesco
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-19 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 15:23 [PATCH] arm64: dts: Add device trees for MSC SM2S-IMX8PLUS SoM and carrier board Martyn Welch
2022-07-19 10:01 ` Krzysztof Kozlowski
2022-07-19 10:15 ` Francesco Dolcini [this message]
2022-07-19 10:18 ` Krzysztof Kozlowski
2022-07-19 16:37 ` Martyn Welch
2022-07-19 18:18 ` Krzysztof Kozlowski
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=YtaEUvP4jpO5Dggg@gaggiata.pivistrello.it \
--to=francesco@dolcini.it \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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