From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Alex Williamson <alex.williamson@redhat.com>,
Jean-Philippe Brucker <jean-philippe@linaro.com>,
Yi Liu <yi.l.liu@intel.com>, "Tian, Kevin" <kevin.tian@intel.com>,
Raj Ashok <ashok.raj@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Jonathan Cameron <jic23@kernel.org>,
Eric Auger <eric.auger@redhat.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v3 3/4] iommu/ioasid: Add custom allocators
Date: Wed, 2 Oct 2019 07:33:38 -0700 [thread overview]
Message-ID: <20191002073338.6bee15f0@jacob-builder> (raw)
In-Reply-To: <20191002141810.GA407870@lophozonia>
On Wed, 2 Oct 2019 16:18:10 +0200
Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> Hi Jacob,
>
> There seem to be a mix-up here, the changes from your v2 are lost and
> patches 1 and 3 are back to v1. Assuming this isn't intended, I'll
> review v2 of this patch since it looked good to me overall.
>
oops, you are right. please review v2.
Thank you!
> Thanks,
> Jean
>
next prev parent reply other threads:[~2019-10-02 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 23:33 [PATCH v3 0/4] User API for nested shared virtual address (SVA) Jacob Pan
2019-10-01 23:33 ` [PATCH v3 1/4] iommu: Introduce cache_invalidate API Jacob Pan
2019-10-01 23:33 ` [PATCH v3 2/4] iommu: Add I/O ASID allocator Jacob Pan
2019-10-01 23:33 ` [PATCH v3 3/4] iommu/ioasid: Add custom allocators Jacob Pan
2019-10-02 14:18 ` Jean-Philippe Brucker
2019-10-02 14:33 ` Jacob Pan [this message]
2019-10-01 23:33 ` [PATCH v3 4/4] iommu: Introduce guest PASID bind function Jacob Pan
2019-10-02 14:22 ` [PATCH v3 0/4] User API for nested shared virtual address (SVA) Jacob Pan
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=20191002073338.6bee15f0@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.com \
--cc=jean-philippe@linaro.org \
--cc=jic23@kernel.org \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@intel.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