Linux IOMMU Development
 help / color / mirror / Atom feed
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,
	Robin Murphy <robin.murphy@arm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH 6/6] iommu: make inclusion of iommufd directory conditional
Date: Mon, 19 May 2025 08:16:39 +0200	[thread overview]
Message-ID: <2782498.mvXUDI8C0e@devpool92.emlix.com> (raw)
In-Reply-To: <aCc0-ClDbiUpNUgh@8bytes.org>

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

On Freitag, 16. Mai 2025 14:52:08 Mitteleuropäische Sommerzeit Joerg Roedel 
wrote:
> On Mon, May 12, 2025 at 03:15:52PM +0200, Rolf Eike Beer wrote:
> > Nothing in there is active if CONFIG_IOMMUFD is not enabled, so the whole
> > directory can depend on that switch as well.
> > 
> > Fixes: 2ff4bed7fee7 ("iommufd: File descriptor, context, kconfig and
> > makefiles") Signed-off-by: Rolf Eike Beer <eb@emlix.com>
> > Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
> 
> Had to remove this patch from the branch as it caused compile breakage
> with allmodconfig builds.

I did not catch that this is a tristate, not a bool. The same happens for 
patch 5, which is what the 0-day bot has reported.

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 --]

  reply	other threads:[~2025-05-19  6:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 13:07 [PATCHv3 0/6] make vendor specific subdirectory inclusion conditional Rolf Eike Beer
2025-05-12 13:10 ` [PATCH 1/6] iommu: remove duplicate selection of DMAR_TABLE Rolf Eike Beer
2025-05-12 13:11 ` [PATCH 2/6] iommu: make inclusion of intel directory conditional Rolf Eike Beer
2025-05-12 13:12 ` [PATCH 3/6] iommu: make inclusion of amd " Rolf Eike Beer
2025-05-12 13:13 ` [PATCH 4/6] iommu: make inclusion of riscv " Rolf Eike Beer
2025-05-12 13:14 ` [PATCH 5/6] iommu: make inclusion of arm/arm-smmu-v3 " Rolf Eike Beer
2025-05-12 13:15 ` [PATCH 6/6] iommu: make inclusion of iommufd " Rolf Eike Beer
2025-05-16 12:52   ` Joerg Roedel
2025-05-19  6:16     ` Rolf Eike Beer [this message]
2025-05-26  5:59     ` Rolf Eike Beer
2025-05-16  6:47 ` [PATCHv3 0/6] make vendor specific subdirectory inclusion conditional Joerg Roedel
  -- strict thread matches above, loose matches on Subject: below --
2025-03-20  9:01 [PATCHv2 " Rolf Eike Beer
2025-03-20  9:22 ` [PATCH 6/6] iommu: make inclusion of iommufd directory conditional Rolf Eike Beer
2025-03-21  2:14   ` Baolu Lu

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=2782498.mvXUDI8C0e@devpool92.emlix.com \
    --to=eb@emlix.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.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