From: Rolf Eike Beer <eb@emlix.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Will Deacon <will@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Tomasz Jeznach <tjeznach@rivosinc.com>,
Nick Kossifidis <mick@ics.forth.gr>,
Sebastien Boeuf <seb@rivosinc.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Subject: Re: [PATCH 4/4] iommu: make inclusion of riscv directory conditional
Date: Thu, 20 Mar 2025 09:10:34 +0100 [thread overview]
Message-ID: <2365431.ElGaqSPkdT@devpool47.emlix.com> (raw)
In-Reply-To: <Z9vMwUQ679SdSwhG@8bytes.org>
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
On Donnerstag, 20. März 2025 09:07:29 Mitteleuropäische Normalzeit Joerg
Roedel wrote:
> On Tue, Mar 11, 2025 at 11:15:12AM +0100, Rolf Eike Beer wrote:
> > Nothing in there is active if CONFIG_RISCV_IOMMU is not enabled, so the
> > whole directory can depend on that switch as well.
> >
> > Fixes: 5c0ebbd3c6c6 ("iommu/riscv: Add RISC-V IOMMU platform device
> > driver") Signed-off-by: Rolf Eike Beer <eb@emlix.com>
> > ---
> >
> > drivers/iommu/Makefile | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/iommu/Makefile b/drivers/iommu/Makefile
> > index 41b00cdc8621..17133876f777 100644
> > --- a/drivers/iommu/Makefile
> > +++ b/drivers/iommu/Makefile
> > @@ -1,7 +1,8 @@
> >
> > # SPDX-License-Identifier: GPL-2.0
> >
> > -obj-y += arm/ iommufd/ riscv/
> > +obj-y += arm/ iommufd/
> >
> > obj-$(CONFIG_AMD_IOMMU) += amd/
> > obj-$(CONFIG_INTEL_IOMMU) += intel/
> >
> > +obj-$(CONFIG_RISCV_IOMMU) += riscv/
> >
> > obj-$(CONFIG_IOMMU_API) += iommu.o
> > obj-$(CONFIG_IOMMU_API) += iommu-traces.o
> > obj-$(CONFIG_IOMMU_API) += iommu-sysfs.o
>
> This allows for some additional cleanups in the Makefiles of the
> sub-directory, no? Same for the other patches in this series.
Yes, and I can send those cleanups as a followup if you like. But for the first
step I wanted to keep this as less invasive as it could be. And to be honest I
didn't want to invest time to do this cleanups if it's unclear if they would
be rejected anyway because these things are this way on purpose.
Regards,
Eike
--
Rolf Eike Beer
emlix GmbH
Headquarters: Berliner Str. 12, 37073 Göttingen, Germany
Phone +49 (0)551 30664-0, e-mail info@emlix.com
District Court of Göttingen, Registry Number HR B 3160
Managing Directors: Heike Jordan, Dr. Uwe Kracke
VAT ID No. DE 205 198 055
Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
Office Bonn: Bachstr. 6, 53115 Bonn, Germany
http://www.emlix.com
emlix - your embedded Linux partner
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 313 bytes --]
next prev parent reply other threads:[~2025-03-20 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 10:04 [PATCH 0/4] make vendor specific subdirectory inclusion conditional Rolf Eike Beer
2025-03-11 10:07 ` [PATCH 1/4] iommu: remove duplicate selection of DMAR_TABLE Rolf Eike Beer
2025-03-11 10:10 ` [PATCH 2/4] iommu: make inclusion of intel directory conditional Rolf Eike Beer
2025-03-11 10:12 ` [PATCH 3/4] iommu: make inclusion of amd " Rolf Eike Beer
2025-03-11 10:15 ` [PATCH 4/4] iommu: make inclusion of riscv " Rolf Eike Beer
2025-03-20 8:07 ` Joerg Roedel
2025-03-20 8:10 ` Rolf Eike Beer [this message]
2025-03-20 8:15 ` 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=2365431.ElGaqSPkdT@devpool47.emlix.com \
--to=eb@emlix.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mick@ics.forth.gr \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=seb@rivosinc.com \
--cc=tjeznach@rivosinc.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