From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Alyssa Rosenzweig <alyssa@rosenzweig.io>,
asahi@lists.linux.dev, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
Shuah Khan <shuah@kernel.org>, Will Deacon <will@kernel.org>,
Eric Auger <eric.auger@redhat.com>, Janne Grunau <j@jannau.net>,
Joerg Roedel <jroedel@suse.de>, Kevin Tian <kevin.tian@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Lixiao Yang <lixiao.yang@intel.com>,
Hector Martin <marcan@marcan.st>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Nicolin Chen <nicolinc@nvidia.com>,
patches@lists.linux.dev, Sven Peter <sven@svenpeter.dev>,
Will Deacon <will.deacon@arm.com>, Yi Liu <yi.l.liu@intel.com>,
Yong Wu <yong.wu@mediatek.com>
Subject: Re: [PATCH rc 0/2] Fix maps created without READ or WRITE
Date: Mon, 26 Aug 2024 09:16:51 +0200 [thread overview]
Message-ID: <Zswr4-fRLI2lHX_Q@8bytes.org> (raw)
In-Reply-To: <0-v1-1211e1294c27+4b1-iommu_no_prot_jgg@nvidia.com>
On Thu, Aug 22, 2024 at 11:45:53AM -0300, Jason Gunthorpe wrote:
> I noticed some bugs here while working on iommupt. Fix them up.
>
> Joerg, can you pick this both for your -rc branch?
Dones, applied to fixes branch, thanks.
prev parent reply other threads:[~2024-08-26 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 14:45 [PATCH rc 0/2] Fix maps created without READ or WRITE Jason Gunthorpe
2024-08-22 14:45 ` [PATCH rc 1/2] iommufd: Do not allow creating areas " Jason Gunthorpe
2024-08-23 16:29 ` Nicolin Chen
2024-08-26 6:20 ` Tian, Kevin
2024-08-22 14:45 ` [PATCH rc 2/2] iommu: Do not return 0 from map_pages if it doesn't do anything Jason Gunthorpe
2024-08-23 16:18 ` Will Deacon
2024-08-26 6:20 ` Tian, Kevin
2024-08-26 7:16 ` Joerg Roedel [this message]
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=Zswr4-fRLI2lHX_Q@8bytes.org \
--to=joro@8bytes.org \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=j@jannau.net \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiao.yang@intel.com \
--cc=marcan@marcan.st \
--cc=mjrosato@linux.ibm.com \
--cc=nicolinc@nvidia.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=shuah@kernel.org \
--cc=sven@svenpeter.dev \
--cc=will.deacon@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yong.wu@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox