From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/9] ARM: dts: imx28: Clean up older DTS files
Date: Tue, 14 Mar 2023 14:43:10 +0800 [thread overview]
Message-ID: <20230314064310.GS143566@dragon> (raw)
In-Reply-To: <20230307184007.10672-1-stefan.wahren@i2se.com>
On Tue, Mar 07, 2023 at 07:39:58PM +0100, Stefan Wahren wrote:
> Since the imx28 belongs to the early ARM platforms which has been
> adapted to DT, a lot of these DTS files are not in the best shape.
> So this series tries to address this by using label references
> and SPDX tags.
>
> Theses patches doesn't include functional changes. The resulting
> DTB files has been verified with dtdiff.
>
> Changes in V2:
> - fix alphabetical order of i2c label reference in patch 1
> - add Wolfgang Grandegger in Cc for patch 2
> - replace Anson's address in patch 7 with linux-imx@nxp.com because
> his address isn't available anymore
> - remove Cc from patch 8 because the address isn't available anymore
> - add Acked-by for patch 9
>
> Stefan Wahren (9):
> ARM: dts: imx28-apf28: Convert to use label references
> ARM: dts: imx28-m28/sps1: Convert to use label references
> ARM: dts: imx28-apx4devkit: Convert to use label references
> ARM: dts: imx28-cfa10036: Convert to use label references
> ARM: dts: imx28-duckbill: Convert to use label references
> ARM: dts: imx28-duckbill-2: Include base board
> ARM: dts: imx28-evk: Convert to use label references
> ARM: dts: imx28-ts4600: Convert to use label references
> ARM: dts: imx28-tx28: add SPDX-License-Identifier
Applied all, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-14 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 18:39 [PATCH V2 0/9] ARM: dts: imx28: Clean up older DTS files Stefan Wahren
2023-03-07 18:39 ` [PATCH V2 1/9] ARM: dts: imx28-apf28: Convert to use label references Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 2/9] ARM: dts: imx28-m28/sps1: " Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 3/9] ARM: dts: imx28-apx4devkit: " Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 4/9] ARM: dts: imx28-cfa10036: " Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 5/9] ARM: dts: imx28-duckbill: " Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 6/9] ARM: dts: imx28-duckbill-2: Include base board Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 7/9] ARM: dts: imx28-evk: Convert to use label references Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 8/9] ARM: dts: imx28-ts4600: " Stefan Wahren
2023-03-07 18:40 ` [PATCH V2 9/9] ARM: dts: imx28-tx28: add SPDX-License-Identifier Stefan Wahren
2023-03-14 6:43 ` Shawn Guo [this message]
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=20230314064310.GS143566@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stefan.wahren@i2se.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).