From: Jon Hunter <jonathanh@nvidia.com>
To: Johan Hovold <johan@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Thierry Reding <thierry.reding@gmail.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 0/2] amba/iommu: tegra: enable compile testing
Date: Mon, 6 Oct 2025 10:39:05 +0100 [thread overview]
Message-ID: <6db8eaff-94e5-49f0-9369-f501e56ca5f2@nvidia.com> (raw)
In-Reply-To: <20250925153120.7129-1-johan@kernel.org>
On 25/09/2025 16:31, Johan Hovold wrote:
> There seems to be nothing preventing us from enabling compile testing of
> the Tegra AHB and IOMMU drivers so enable that to increase build
> coverage.
>
> Note that these could go in through separate trees, but compile testing
> of the IOMMU driver does depend on the AHB driver being enabled.
>
> Johan
>
>
> Johan Hovold (2):
> amba: tegra-ahb: enable compile testing
> iommu: tegra: enable compile testing
>
> drivers/amba/Kconfig | 2 +-
> drivers/iommu/Kconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Looks good to me.
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2025-10-06 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:31 [PATCH 0/2] amba/iommu: tegra: enable compile testing Johan Hovold
2025-09-25 15:31 ` [PATCH 1/2] amba: tegra-ahb: " Johan Hovold
2025-09-25 15:31 ` [PATCH 2/2] iommu: tegra: " Johan Hovold
2025-10-27 11:19 ` Joerg Roedel
2025-09-30 18:22 ` [PATCH 0/2] amba/iommu: " Jason Gunthorpe
2025-10-06 9:39 ` Jon Hunter [this message]
2025-10-27 13:40 ` Johan Hovold
2025-10-27 14:11 ` Joerg Roedel
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=6db8eaff-94e5-49f0-9369-f501e56ca5f2@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=johan@kernel.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=thierry.reding@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).