mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Francesco Lavra <flavra@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Kartik Rajput <kkartik@nvidia.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Robert Marko <robert.marko@sartura.hr>,
	Thierry Bultel <thierry.bultel.yh@bp.renesas.com>,
	Douglas Anderson <dianders@chromium.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] serial: tegra: remove Kconfig dependency on APB DMA controller
Date: Thu, 26 Feb 2026 10:04:38 +0000	[thread overview]
Message-ID: <85ea9062-1e16-4757-988d-8a170a546e04@nvidia.com> (raw)
In-Reply-To: <20251126090759.4042709-1-flavra@baylibre.com>


On 26/11/2025 09:07, Francesco Lavra wrote:
> This driver runs also on SoCs without a Tegra20 APB DMA controller (e.g.
> Tegra234).
> Remove the Kconfig dependency on TEGRA20_APB_DMA, and remove reference to
> the APB DMA controller from the Kconfig help text.
> 
> Fixes: 60d2016a5161 ("arm64: tegra: Add Tegra234 GPCDMA device tree node")

This patch looks fine, but I would drop the fixes tag. 	There are other 
earlier devices, such as Tegra186 that also use this. Also please CC 
linux-tegra@vger.kernel.org on these patches too. I know people try to 
limit the number of list copied, but we may miss this otherwise.

Thanks
Jon

-- 
nvpublic


      parent reply	other threads:[~2026-02-26 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  9:07 Francesco Lavra
2025-11-26 11:20 ` Andy Shevchenko
2025-11-26 12:08   ` Francesco Lavra
2025-11-26 16:25     ` Andy Shevchenko
2025-11-26 16:45       ` Francesco Lavra
2025-11-26 17:44         ` Andy Shevchenko
2026-02-25 11:35 ` Francesco Lavra
2026-03-12 13:43   ` Greg Kroah-Hartman
2026-03-13  7:56     ` Francesco Lavra
2026-02-26 10:04 ` 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=85ea9062-1e16-4757-988d-8a170a546e04@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dianders@chromium.org \
    --cc=flavra@baylibre.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kkartik@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robert.marko@sartura.hr \
    --cc=thierry.bultel.yh@bp.renesas.com \
    --cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®