From: Conor Dooley <conor@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] dt-bindings: tegra: Document Jetson Orin Nano Developer Kit
Date: Tue, 16 May 2023 22:24:48 +0100 [thread overview]
Message-ID: <20230516-trickery-untrained-aa55b6084f1e@spud> (raw)
In-Reply-To: <20230516095850.2426604-3-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 358 bytes --]
On Tue, May 16, 2023 at 11:58:49AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The Jetson Orin Nano Developer Kit pairs the Jetson Orin Nano devkit
> module with the P3768 carrier board.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-16 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:58 [PATCH v2 0/3] arm64: tegra: Support Jetson Orin Nano Developer Kit Thierry Reding
2023-05-16 9:58 ` [PATCH v2 1/3] dt-bindings: tegra: Document Jetson Orin Nano Thierry Reding
2023-05-16 21:25 ` Conor Dooley
2023-05-17 8:49 ` Krzysztof Kozlowski
2023-05-16 9:58 ` [PATCH v2 2/3] dt-bindings: tegra: Document Jetson Orin Nano Developer Kit Thierry Reding
2023-05-16 21:24 ` Conor Dooley [this message]
2023-05-16 9:58 ` [PATCH v2 3/3] arm64: tegra: Support " Thierry Reding
2023-06-06 13:03 ` (subset) [PATCH v2 0/3] " Thierry Reding
2023-06-06 13:06 ` 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=20230516-trickery-untrained-aa55b6084f1e@spud \
--to=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).