From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Cornelia Huck <cohuck@redhat.com>,
iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
Nicolin Chen <nicolinc@nvidia.com>, Will Deacon <will@kernel.org>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH] vfio: Remove VFIO_TYPE1_NESTING_IOMMU
Date: Fri, 20 May 2022 09:38:09 +0200 [thread overview]
Message-ID: <YodFYVd4vLetqt3D@8bytes.org> (raw)
In-Reply-To: <20220517142656.140deb10.alex.williamson@redhat.com>
On Tue, May 17, 2022 at 02:26:56PM -0600, Alex Williamson wrote:
> I'd be in favor of applying this, but it seems Robin and Eric are
> looking for a stay of execution and I'd also be looking for an ack from
> Joerg. Thanks,
This is mainly an ARM-SMMU thing, so I defer my ack to Will and Robin.
Regards,
Joerg
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-20 7:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 16:55 [PATCH] vfio: Remove VFIO_TYPE1_NESTING_IOMMU Jason Gunthorpe
2022-05-10 17:52 ` Robin Murphy
2022-05-10 18:13 ` Jason Gunthorpe
2022-05-12 7:07 ` Zhangfei Gao
2022-05-12 11:32 ` Jason Gunthorpe
2022-05-12 11:57 ` zhangfei.gao
2022-05-12 11:59 ` Jason Gunthorpe
2022-05-12 12:07 ` zhangfei.gao
2022-05-12 17:27 ` Eric Auger
2022-05-10 18:31 ` Nicolin Chen
2022-05-12 5:04 ` Tian, Kevin
2022-05-16 6:39 ` Christoph Hellwig
2022-05-17 20:26 ` Alex Williamson
2022-05-20 7:38 ` Joerg Roedel [this message]
2022-05-20 11:02 ` Robin Murphy
2022-05-20 12:00 ` Will Deacon
2022-05-20 12:28 ` Jason Gunthorpe
2022-05-20 12:18 ` Jason Gunthorpe
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=YodFYVd4vLetqt3D@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nicolinc@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).