From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
thierry.reding@gmail.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add GPCDMA support for Tegra234
Date: Thu, 12 May 2022 10:21:50 +0100 [thread overview]
Message-ID: <2e082196-1566-c18d-3793-028f07c1926c@nvidia.com> (raw)
In-Reply-To: <2e2cac21-1071-546b-7091-8be26860f5f0@nvidia.com>
On 12/05/2022 10:09, Jon Hunter wrote:
>
>
> On 12/05/2022 10:00, Akhil R wrote:
>> Add headers and device tree node to support GPCDMA in Tegra234
>>
>> Akhil R (2):
>> dt-bindings: Add headers for Tegra234 GPCDMA
>> arm64: tegra: Add Tegra234 GPCDMA device tree node
>>
>> arch/arm64/boot/dts/nvidia/tegra234.dtsi | 43 ++++++++++++++++++++++
>> include/dt-bindings/memory/tegra234-mc.h | 1 +
>> include/dt-bindings/reset/tegra234-reset.h | 1 +
>> 3 files changed, 45 insertions(+)
>>
>
> This should be V2 right? Otherwise looks good to me.
Ah sorry, I forgot the initial version you sent me was not published to
the external mailing list so this is V1.
Jon
--
nvpublic
prev parent reply other threads:[~2022-05-12 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 9:00 [PATCH 0/2] Add GPCDMA support for Tegra234 Akhil R
2022-05-12 9:00 ` [PATCH 1/2] dt-bindings: Add headers for Tegra234 GPCDMA Akhil R
2022-05-13 8:32 ` Krzysztof Kozlowski
2022-05-12 9:00 ` [PATCH 2/2] arm64: tegra: Add Tegra234 GPCDMA device tree node Akhil R
2022-05-13 8:32 ` Krzysztof Kozlowski
2022-05-13 8:39 ` Jon Hunter
2022-05-13 9:14 ` Krzysztof Kozlowski
2022-05-12 9:09 ` [PATCH 0/2] Add GPCDMA support for Tegra234 Jon Hunter
2022-05-12 9:21 ` Jon Hunter [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=2e082196-1566-c18d-3793-028f07c1926c@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.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).