From: Shawn Guo <shawnguo@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-usb <linux-usb@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] dt-bindings: usb: dwc3-imx8mp: Use the correct name for child node "snps,dwc3"
Date: Mon, 26 Apr 2021 09:21:39 +0800 [thread overview]
Message-ID: <20210426012138.GA27585@dragon> (raw)
In-Reply-To: <20210329072714.2135-1-thunder.leizhen@huawei.com>
On Mon, Mar 29, 2021 at 03:27:12PM +0800, Zhen Lei wrote:
> File snps,dwc3.yaml describes the schema of Synopsys DesignWare USB3
> Controller, it directly or indirectly contains "$ref: usb.yaml". So the
> node name of "snps,dwc3" must start with "usb". Otherwise, the following
> warning will be displayed:
>
> Documentation/devicetree/bindings/usb/fsl,imx8mp-dwc3.example.dt.yaml: \
> dwc3@38100000: $nodename:0: 'dwc3@38100000' does not match '^usb(@.*)?'
> From schema: Documentation/devicetree/bindings/usb/snps,dwc3.yaml
>
>
> Zhen Lei (2):
> dt-bindings: usb: dwc3-imx8mp: Use the correct name for child node
> "snps,dwc3"
> arm64: dts: imx8mp: Use the correct name for child node "snps,dwc3"
Applied both, thanks.
prev parent reply other threads:[~2021-04-26 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 7:27 [PATCH 0/2] dt-bindings: usb: dwc3-imx8mp: Use the correct name for child node "snps,dwc3" Zhen Lei
2021-03-29 7:27 ` [PATCH 1/2] " Zhen Lei
2021-03-30 22:03 ` [PATCH 1/2] dt-bindings: usb: dwc3-imx8mp: Use the correct name for child node "snps, dwc3" Rob Herring
2021-03-29 7:27 ` [PATCH 2/2] arm64: dts: imx8mp: Use the correct name for child node "snps,dwc3" Zhen Lei
2021-04-26 1:21 ` 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=20210426012138.GA27585@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=thunder.leizhen@huawei.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).