From: Baolu Lu <baolu.lu@linux.intel.com>
To: Rolf Eike Beer <eb@emlix.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Bert Karwatzki <spasswolf@web.de>
Subject: Re: [PATCH 1/6] iommu: remove duplicate selection of DMAR_TABLE
Date: Fri, 21 Mar 2025 09:56:41 +0800 [thread overview]
Message-ID: <fcb6a265-8b87-43df-83d5-1b10adee3911@linux.intel.com> (raw)
In-Reply-To: <2797918.mvXUDI8C0e@devpool47.emlix.com>
On 3/20/25 17:05, Rolf Eike Beer wrote:
> This is already done in intel/Kconfig.
>
> Fixes: 70bad345e622 ("iommu: Fix compilation without CONFIG_IOMMU_INTEL")
> Signed-off-by: Rolf Eike Beer<eb@emlix.com>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
next prev parent reply other threads:[~2025-03-21 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 9:01 [PATCHv2 0/6] make vendor specific subdirectory inclusion conditional Rolf Eike Beer
2025-03-20 9:05 ` [PATCH 1/6] iommu: remove duplicate selection of DMAR_TABLE Rolf Eike Beer
2025-03-21 1:56 ` Baolu Lu [this message]
2025-03-20 9:07 ` [PATCH 2/6] iommu: make inclusion of intel directory conditional Rolf Eike Beer
2025-03-21 2:04 ` Baolu Lu
2025-03-20 9:14 ` [PATCH 3/6] iommu: make inclusion of amd " Rolf Eike Beer
2025-03-21 2:06 ` Baolu Lu
2025-03-20 9:16 ` [PATCH 4/6] iommu: make inclusion of riscv " Rolf Eike Beer
2025-03-21 2:08 ` Baolu Lu
2025-03-20 9:19 ` [PATCH 5/6] iommu: make inclusion of arm/arm-smmu-v3 " Rolf Eike Beer
2025-03-21 2:11 ` Baolu Lu
2025-03-20 9:22 ` [PATCH 6/6] iommu: make inclusion of iommufd " Rolf Eike Beer
2025-03-21 2:14 ` Baolu Lu
2025-04-17 14:32 ` [PATCHv2 0/6] make vendor specific subdirectory inclusion conditional Joerg Roedel
2025-04-22 6:35 ` Rolf Eike Beer
-- strict thread matches above, loose matches on Subject: below --
2025-05-12 13:07 [PATCHv3 " Rolf Eike Beer
2025-05-12 13:10 ` [PATCH 1/6] iommu: remove duplicate selection of DMAR_TABLE Rolf Eike Beer
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=fcb6a265-8b87-43df-83d5-1b10adee3911@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=eb@emlix.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spasswolf@web.de \
--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