From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 5/5] dt-bindings: arm: tegra: Add missing compatible strings
Date: Tue, 12 Jul 2022 10:30:04 +0200 [thread overview]
Message-ID: <131bb7a0-e16e-187e-d48d-286440e8e6da@linaro.org> (raw)
In-Reply-To: <20220711152020.688461-5-thierry.reding@gmail.com>
On 11/07/2022 17:20, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The Nyan Blaze and Nyan Big, as well as Jetson Nano (P3450-0000), Darcy
> (P2894-0050-A08) and Pixel C (Smaug) were never mentioned. Add them.
>
> While at it, also fix a typo in the compatible string for Apalis Tegra30
> v1.1 evaluation board.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-12 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:20 [PATCH 1/5] dt-bindings: arm: tegra: flowctrl: Convert to json-schema Thierry Reding
2022-07-11 15:20 ` [PATCH 2/5] dt-bindings: arm: tegra: ahb: " Thierry Reding
2022-07-12 8:20 ` Krzysztof Kozlowski
2022-07-11 15:20 ` [PATCH 3/5] dt-bindings: arm: tegra: nvec: " Thierry Reding
2022-07-12 8:24 ` Krzysztof Kozlowski
2022-07-17 21:31 ` Marc Dietrich
2022-07-11 15:20 ` [PATCH 4/5] dt-bindings: arm: tegra: Revise Tegra20 PMC bindings Thierry Reding
2022-07-12 8:28 ` Krzysztof Kozlowski
2022-07-11 15:20 ` [PATCH 5/5] dt-bindings: arm: tegra: Add missing compatible strings Thierry Reding
2022-07-11 15:36 ` Francesco Dolcini
2022-07-11 16:41 ` Thierry Reding
2022-07-12 8:30 ` Krzysztof Kozlowski [this message]
2022-07-12 8:19 ` [PATCH 1/5] dt-bindings: arm: tegra: flowctrl: Convert to json-schema Krzysztof Kozlowski
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=131bb7a0-e16e-187e-d48d-286440e8e6da@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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).