From: Shawn Guo <shawnguo@kernel.org>
To: Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
Varun Sethi <V.Sethi@nxp.com>, Leo Li <leoyang.li@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Kuldeep Singh <kuldeep.singh@nxp.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: lx2160a: add device tree for lx2162aqds board
Date: Mon, 26 Oct 2020 15:18:40 +0800 [thread overview]
Message-ID: <20201026071839.GE9880@dragon> (raw)
In-Reply-To: <AM7PR04MB6885980FC5B035B955D009BA8E1E0@AM7PR04MB6885.eurprd04.prod.outlook.com>
On Mon, Oct 19, 2020 at 09:00:33AM +0000, Meenakshi Aggarwal wrote:
> Hi,
>
> Any further comments?
Please address the following checkpatch warnings.
WARNING: DT compatible string "nxp,lx2162a-qds" appears un-documented -- check ./Documentation/devicetree/bindings/
#49: FILE: arch/arm64/boot/dts/freescale/fsl-lx2162a-qds.dts:13:
+ compatible = "nxp,lx2162a-qds", "fsl,lx2160a";
WARNING: DT compatible string "ethernet-phy-id001c.c916" appears un-documented -- check ./Documentation/devicetree/bindings/
#80: FILE: arch/arm64/boot/dts/freescale/fsl-lx2162a-qds.dts:44:
+ compatible = "ethernet-phy-id001c.c916";
WARNING: DT compatible string "ethernet-phy-id001c.c916" appears un-documented -- check ./Documentation/devicetree/bindings/
#92: FILE: arch/arm64/boot/dts/freescale/fsl-lx2162a-qds.dts:56:
+ compatible = "ethernet-phy-id001c.c916";
Shawn
next prev parent reply other threads:[~2020-10-26 7:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:13 [PATCH 1/2] dt-bindings: arm64: add compatible for LX2162A QDS Board meenakshi.aggarwal
2020-09-02 15:13 ` [PATCH 2/2] arm64: dts: lx2160a: add device tree for lx2162aqds board meenakshi.aggarwal
2020-09-05 7:54 ` Shawn Guo
2020-09-09 7:10 ` Meenakshi Aggarwal
2020-09-12 9:49 ` Shawn Guo
2020-09-21 6:00 ` Meenakshi Aggarwal
2020-09-21 13:03 ` Shawn Guo
2020-09-21 13:34 ` Meenakshi Aggarwal
2020-09-29 10:01 ` [PATCH v3 0/2] Add device tree support for LX2162AQDS board meenakshi.aggarwal
2020-09-29 10:01 ` [PATCH v3 1/2] dt-bindings: arm64: add compatible for LX2162A QDS Board meenakshi.aggarwal
2020-09-29 10:01 ` [PATCH v3 2/2] arm64: dts: lx2160a: add device tree for lx2162aqds board meenakshi.aggarwal
2020-10-19 9:00 ` Meenakshi Aggarwal
2020-10-26 7:18 ` Shawn Guo [this message]
2020-10-26 14:35 ` Leo Li
2020-10-30 8:59 ` Meenakshi Aggarwal
2020-11-02 5:59 ` [PATCH v4 0/2] Add device tree support for LX2162AQDS board meenakshi.aggarwal
2020-11-02 5:59 ` [PATCH v4 1/2] dt-bindings: arm64: add compatible for LX2162A QDS Board meenakshi.aggarwal
2020-11-02 5:59 ` [PATCH v4 2/2] arm64: dts: lx2160a: add device tree for lx2162aqds board meenakshi.aggarwal
2020-11-02 23:25 ` [PATCH v4 0/2] Add device tree support for LX2162AQDS board Shawn Guo
2020-09-14 20:23 ` [PATCH 1/2] dt-bindings: arm64: add compatible for LX2162A QDS Board Rob Herring
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=20201026071839.GE9880@dragon \
--to=shawnguo@kernel.org \
--cc=V.Sethi@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=kuldeep.singh@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meenakshi.aggarwal@nxp.com \
--cc=robh+dt@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).