All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@nvidia.com>, joro@8bytes.org
Cc: baolu.lu@linux.intel.com, kevin.tian@intel.com,
	robin.murphy@arm.com, will@kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH] iommu/vt-d: Restore IOMMU_CAP_CACHE_COHERENCY
Date: Wed, 8 Apr 2026 20:49:38 -0300	[thread overview]
Message-ID: <20260408234938.GH3357077@nvidia.com> (raw)
In-Reply-To: <20260408184443.3077333-1-alex.williamson@nvidia.com>

On Wed, Apr 08, 2026 at 12:44:42PM -0600, Alex Williamson wrote:
> In removing IOMMU_CAP_DEFERRED_FLUSH, the below referenced commit
> was over-eager in removing the return, resulting in the test for
> IOMMU_CAP_CACHE_COHERENCY falling through to an irrelevant option.
> 
> Restore dropped return.
> 
> Fixes: 1c18a1212c77 ("iommu/dma: Always allow DMA-FQ when iommupt provides the iommu_domain")
> Signed-off-by: Alex Williamson <alex.williamson@nvidia.com>

I didn't think this was merged - I didn't get an email about it? Joerg
I've noticed alot of silent merges from you lately is that deliberate
or is something wrong?

But yes this is right:

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Kevin and I both missed it!!

Thanks,
Jason

  reply	other threads:[~2026-04-08 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 18:44 [PATCH] iommu/vt-d: Restore IOMMU_CAP_CACHE_COHERENCY Alex Williamson
2026-04-08 23:49 ` Jason Gunthorpe [this message]
2026-04-09  1:46   ` Tian, Kevin
2026-04-09  3:19 ` Baolu Lu
2026-04-09 13:01 ` Will Deacon

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=20260408234938.GH3357077@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@nvidia.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --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 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.