From: Alice Guo <alice.guo@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [EXT] Re: [PATCH v3 2/4] arm64: dts: imx8m: add compatible string to .dtsi file
Date: Mon, 16 Nov 2020 07:12:25 +0000 [thread overview]
Message-ID: <AM6PR04MB6053C4B217108356215600BAE2E30@AM6PR04MB6053.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201114155723.GB14989@kozik-lap>
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: 2020年11月14日 23:57
> To: Alice Guo <alice.guo@nxp.com>
> Cc: robh+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> dl-linux-imx <linux-imx@nxp.com>; Peng Fan <peng.fan@nxp.com>;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org
> Subject: [EXT] Re: [PATCH v3 2/4] arm64: dts: imx8m: add compatible string
> to .dtsi file
>
> Caution: EXT Email
>
> On Fri, Nov 13, 2020 at 07:04:07PM +0800, Alice Guo wrote:
>
> Where is the changelog against v2?
>
> Change the subject to: "arm64: dts: imx8m: add SoC ID compatible". It is kind
> of obvious that you add it to DTSI files, so no need to put it into the subject.
>
> > Add compatible string to .dtsi file for binding of
> > imx8_soc_init_driver and device.
>
> s/file/files/
>
> With above changes:
> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
[Alice Guo] Hi,
I will modify according to your comment.
Best regards,
Alice
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2020-11-16 7:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 11:04 [PATCH v3 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID Alice Guo
2020-11-13 11:04 ` [PATCH v3 2/4] arm64: dts: imx8m: add compatible string to .dtsi file Alice Guo
2020-11-14 15:57 ` Krzysztof Kozlowski
2020-11-16 7:12 ` Alice Guo [this message]
2020-11-13 11:04 ` [PATCH v3 3/4] arm64: dts: imx8m: add nvmem-cell related stuff Alice Guo
2020-11-14 16:00 ` Krzysztof Kozlowski
2020-11-16 7:16 ` [EXT] " Alice Guo
2020-11-13 11:04 ` [PATCH v3 4/4] soc: imx8m: change to use platform driver Alice Guo
2020-11-14 16:41 ` Krzysztof Kozlowski
2020-11-16 8:18 ` [EXT] " Alice Guo
2020-11-16 16:13 ` Krzysztof Kozlowski
2020-11-18 10:28 ` Alice Guo
2020-11-18 10:42 ` Krzysztof Kozlowski
2020-11-18 14:07 ` Alice Guo
2020-11-18 14:10 ` Krzysztof Kozlowski
2020-11-19 7:32 ` Alice Guo
2020-11-19 9:42 ` Krzysztof Kozlowski
2020-11-14 15:55 ` [PATCH v3 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID Krzysztof Kozlowski
2020-11-14 16:49 ` Krzysztof Kozlowski
2020-11-16 7:04 ` [EXT] " Alice Guo
2020-11-16 16:03 ` Krzysztof Kozlowski
2020-11-17 7:12 ` Alice Guo
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=AM6PR04MB6053C4B217108356215600BAE2E30@AM6PR04MB6053.eurprd04.prod.outlook.com \
--to=alice.guo@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.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;
as well as URLs for NNTP newsgroup(s).