From: Joerg Roedel <joro@8bytes.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Jason Gunthorpe <jgg@nvidia.com>, Li Yang <leoyang.li@nxp.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
iommu@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
Nicholas Piggin <npiggin@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 0/3] Remove iommu_group_remove_device() from fsl
Date: Thu, 1 Jun 2023 11:48:28 +0200 [thread overview]
Message-ID: <ZHhpbAqrIPp33iit@8bytes.org> (raw)
In-Reply-To: <87leh5yobf.fsf@mail.lhotse>
On Wed, May 31, 2023 at 05:04:04PM +1000, Michael Ellerman wrote:
> Great, yep consider it:
>
> Tested-by: Michael Ellerman <mpe@ellerman.id.au>
Alright, applied them for 6.5.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Nicholas Piggin <npiggin@gmail.com>, Li Yang <leoyang.li@nxp.com>,
iommu@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/3] Remove iommu_group_remove_device() from fsl
Date: Thu, 1 Jun 2023 11:48:28 +0200 [thread overview]
Message-ID: <ZHhpbAqrIPp33iit@8bytes.org> (raw)
In-Reply-To: <87leh5yobf.fsf@mail.lhotse>
On Wed, May 31, 2023 at 05:04:04PM +1000, Michael Ellerman wrote:
> Great, yep consider it:
>
> Tested-by: Michael Ellerman <mpe@ellerman.id.au>
Alright, applied them for 6.5.
next prev parent reply other threads:[~2023-06-01 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 0:35 [PATCH v2 0/3] Remove iommu_group_remove_device() from fsl Jason Gunthorpe
2023-05-17 0:35 ` [PATCH v2 1/3] iommu/fsl: Always allocate a group for non-pci devices Jason Gunthorpe
2023-05-17 0:35 ` [PATCH v2 2/3] iommu/fsl: Move ENODEV to fsl_pamu_probe_device() Jason Gunthorpe
2023-05-17 0:35 ` [PATCH v2 3/3] iommu/fsl: Use driver_managed_dma to allow VFIO to work Jason Gunthorpe
2023-05-23 6:26 ` [PATCH v2 0/3] Remove iommu_group_remove_device() from fsl Joerg Roedel
2023-05-23 6:26 ` Joerg Roedel
2023-05-29 0:46 ` Jason Gunthorpe
2023-05-29 0:46 ` Jason Gunthorpe
2023-05-30 12:03 ` Michael Ellerman
2023-05-30 12:03 ` Michael Ellerman
2023-05-30 13:43 ` Jason Gunthorpe
2023-05-30 13:43 ` Jason Gunthorpe
2023-05-31 7:04 ` Michael Ellerman
2023-05-31 7:04 ` Michael Ellerman
2023-06-01 9:48 ` Joerg Roedel [this message]
2023-06-01 9:48 ` Joerg Roedel
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=ZHhpbAqrIPp33iit@8bytes.org \
--to=joro@8bytes.org \
--cc=christophe.leroy@csgroup.eu \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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.