From: Joerg Roedel <joro@8bytes.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
shameerali.kolothum.thodi@huawei.com, alex.williamson@redhat.com,
robin.murphy@arm.com, hch@infradead.org
Subject: Re: [PATCH v3] iommu: revisit iommu_insert_resv_region() implementation
Date: Fri, 30 Aug 2019 15:50:22 +0200 [thread overview]
Message-ID: <20190830135022.GB11578@8bytes.org> (raw)
In-Reply-To: <20190821120940.22337-1-eric.auger@redhat.com>
On Wed, Aug 21, 2019 at 02:09:40PM +0200, Eric Auger wrote:
> drivers/iommu/iommu.c | 96 +++++++++++++++++++++----------------------
> 1 file changed, 47 insertions(+), 49 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2019-08-30 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 12:09 [PATCH v3] iommu: revisit iommu_insert_resv_region() implementation Eric Auger
2019-08-26 6:38 ` Christoph Hellwig
2019-08-30 13:50 ` 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=20190830135022.GB11578@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.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