From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dipen Patel <dipenp@nvidia.com>,
Suneel Garapati <suneelg@nvidia.com>,
jonathanh@nvidia.com, thierry.reding@gmail.com,
krzk+dt@kernel.org, conor+dt@kernel.org, amhetre@nvidia.com,
sheetal@nvidia.com, kkarthik@nvidia.com,
timestamp@list.linux.dev, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH 2/3] hte: tegra194: Add Tegra264 GTE support
Date: Mon, 30 Mar 2026 20:39:43 +0200 [thread overview]
Message-ID: <3f88abb3-fcc4-4d73-b003-84fc0bd28306@kernel.org> (raw)
In-Reply-To: <6bbff5d0-c75d-42ef-8877-de60e7113db4@nvidia.com>
On 30/03/2026 20:35, Dipen Patel wrote:
>> MODULE_DEVICE_TABLE(of, tegra_hte_of_match);
Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.
> Acked-by: Dipen Patel <dipenp@nvidia.com>
> Signed-off-by: Dipen Patel <dipenp@nvidia.com>
What are you certifying here with SoB?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-30 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260330170657.185854-1-suneelg@nvidia.com>
[not found] ` <20260330170657.185854-3-suneelg@nvidia.com>
2026-03-30 18:35 ` [PATCH 2/3] hte: tegra194: Add Tegra264 GTE support Dipen Patel
2026-03-30 18:39 ` Krzysztof Kozlowski [this message]
2026-03-30 19:32 ` Dipen Patel
2026-03-30 19:33 ` Krzysztof Kozlowski
2026-03-31 17:35 ` Dipen Patel
[not found] ` <20260330170657.185854-4-suneelg@nvidia.com>
2026-03-31 19:33 ` [PATCH 3/3] arm64: tegra: Add GTE nodes for Tegra264 Dipen Patel
2026-04-01 21:38 [PATCH 0/3] Add Tegra264 HTE provider Suneel Garapati
2026-04-01 21:38 ` [PATCH 2/3] hte: tegra194: Add Tegra264 GTE support Suneel Garapati
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=3f88abb3-fcc4-4d73-b003-84fc0bd28306@kernel.org \
--to=krzk@kernel.org \
--cc=amhetre@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kkarthik@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sheetal@nvidia.com \
--cc=suneelg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=timestamp@list.linux.dev \
/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