From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
linux-tegra@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] dt-bindings: usb: tegra-xusb: Remove path references
Date: Fri, 16 Dec 2022 11:40:34 -0600 [thread overview]
Message-ID: <20221216174034.GA2986753-robh@kernel.org> (raw)
In-Reply-To: <20221130154111.1655603-1-thierry.reding@gmail.com>
On Wed, Nov 30, 2022 at 04:41:11PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Unresolved path references are now flagged as errors when checking the
> device tree binding examples, so convert them into label references.
>
> Reported-by: Conor Dooley <conor.dooley@microchip.com>
> Suggested-by: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/usb/nvidia,tegra124-xusb.yaml | 4 +---
> .../devicetree/bindings/usb/nvidia,tegra186-xusb.yaml | 4 +---
> .../devicetree/bindings/usb/nvidia,tegra194-xusb.yaml | 8 ++------
> .../devicetree/bindings/usb/nvidia,tegra210-xusb.yaml | 8 ++------
> 4 files changed, 6 insertions(+), 18 deletions(-)
As this is the only binding issue remaining in Linus's tree and it's the
only thing in the Tegra tree, I've applied it for rc1.
Rob
next prev parent reply other threads:[~2022-12-16 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 15:41 [PATCH] dt-bindings: usb: tegra-xusb: Remove path references Thierry Reding
2022-11-30 15:43 ` Krzysztof Kozlowski
2022-11-30 16:39 ` Geert Uytterhoeven
2022-11-30 20:48 ` Rob Herring
2022-12-16 17:40 ` Rob Herring [this message]
2022-12-21 9:18 ` Thierry Reding
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=20221216174034.GA2986753-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thierry.reding@gmail.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).