From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Peter Robinson" <pbrobinson@gmail.com>, <linux-tegra@vger.kernel.org>
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
"Thierry Reding" <treding@nvidia.com>,
"Sameer Pujar" <spujar@nvidia.com>,
"Laxman Dewangan" <ldewangan@nvidia.com>,
"Vinod Koul" <vkoul@kernel.org>, <dmaengine@vger.kernel.org>
Subject: Re: [PATCH 2/2] dmaengine: tegra210-adma: Update dependency to ARCH_TEGRA
Date: Fri, 16 Feb 2024 11:50:08 +0100 [thread overview]
Message-ID: <CZ6G1IYIUZ34.E9WAQS7JJV2Q@gmail.com> (raw)
In-Reply-To: <20240216100246.568473-2-pbrobinson@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
On Fri Feb 16, 2024 at 11:02 AM CET, Peter Robinson wrote:
> Update the architecture dependency to be the generic Tegra
> because the driver works on the four latest Tegra generations
> not just Tegra210, if you build a kernel with a specific
> ARCH_TEGRA_xxx_SOC option that excludes Tegra210 you don't get
> this driver.
>
> Fixes: 433de642a76c9 ("dmaengine: tegra210-adma: add support for Tegra186/Tegra194")
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> Cc: Jon Hunter <jonathanh@nvidia.com>
> Cc: Thierry Reding <treding@nvidia.com>
> Cc: Sameer Pujar <spujar@nvidia.com>
> Cc: Laxman Dewangan <ldewangan@nvidia.com>
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> ---
>
> v2: fix spelling of option
> v3: Update T210 -> Tegra210
> use "and later" rather than all current devices
>
> drivers/dma/Kconfig | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-16 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 10:02 [PATCH 1/2] bus: tegra-aconnect: Update dependency to ARCH_TEGRA Peter Robinson
2024-02-16 10:02 ` [PATCH 2/2] dmaengine: tegra210-adma: " Peter Robinson
2024-02-16 10:50 ` Thierry Reding [this message]
2024-02-16 12:25 ` Vinod Koul
2024-02-16 11:12 ` (subset) [PATCH 1/2] bus: tegra-aconnect: " 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=CZ6G1IYIUZ34.E9WAQS7JJV2Q@gmail.com \
--to=thierry.reding@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=spujar@nvidia.com \
--cc=treding@nvidia.com \
--cc=vkoul@kernel.org \
/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