All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Joerg Roedel <joro@8bytes.org>,
	iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>
Subject: Re: [GIT PULL] Please pull IOMMUFD shared branch
Date: Fri, 28 Feb 2025 13:13:57 -0400	[thread overview]
Message-ID: <20250228171357.GA39591@nvidia.com> (raw)
In-Reply-To: <9ee55e38-b92d-45e1-80df-a6d08c9baccc@arm.com>

On Fri, Feb 28, 2025 at 04:01:43PM +0000, Robin Murphy wrote:
> > Jason Gunthorpe (5):
> >        genirq/msi: Store the IOMMU IOVA directly in msi_desc instead of iommu_cookie
> >        genirq/msi: Refactor iommu_dma_compose_msi_msg()
> >        iommu: Make iommu_dma_prepare_msi() into a generic operation
> 
> So we're just merging this anyway despite it getting no review other than my
> objection to it? Oh well...

Thomas reviewed the first two patches, Joerg acked the whole
series. Nicolin reviewed the third series. It's been on the list since
Jan 10.

It was already in my tree and pushed out *before* you started making
comments.

Patch 7 that seemed to have the most problems was dropped.

We all promised to fix your style concerns in patch 3. I thought that
discussion was agreed that would be done after since we need some new
infrastructure.There are already 3 series trying to figure that out,
so I think it is likely one of them will go along with this merge
window.

People are waiting on this work. It is fixing bugs and problems that
prevent actually rolling out years of effort here.

Jason

  reply	other threads:[~2025-02-28 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:29 [GIT PULL] Please pull IOMMUFD shared branch Jason Gunthorpe
2025-02-28 15:36 ` Joerg Roedel
2025-02-28 16:01 ` Robin Murphy
2025-02-28 17:13   ` Jason Gunthorpe [this message]
2025-02-28 18:06 ` Nicolin Chen
2025-02-28 19:13   ` Nicolin Chen

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=20250228171357.GA39591@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=robin.murphy@arm.com \
    /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.