From: Joerg Roedel <joro@8bytes.org>
To: Rolf Eike Beer <eb@emlix.com>
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:15:37 +0100 [thread overview]
Message-ID: <Z9vOqabp0GwimC1J@8bytes.org> (raw)
In-Reply-To: <2365431.ElGaqSPkdT@devpool47.emlix.com>
On Thu, Mar 20, 2025 at 09:10:34AM +0100, Rolf Eike Beer wrote:
> 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.
I am fine with these cleanups and they are contained enough to also take
care of the vendor-specific Makefiles in the same series.
Regards,
Joerg
prev parent reply other threads:[~2025-03-20 8:15 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
2025-03-20 8:15 ` Joerg Roedel [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=Z9vOqabp0GwimC1J@8bytes.org \
--to=joro@8bytes.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=eb@emlix.com \
--cc=iommu@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.