From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Raj Ashok <ashok.raj@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Jean-Philippe Brucker <jean-philippe@linaro.com>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v4 0/4] User API for nested shared virtual address (SVA)
Date: Tue, 15 Oct 2019 09:56:41 +0200 [thread overview]
Message-ID: <20191015075641.GC1467695@lophozonia> (raw)
In-Reply-To: <20191014101405.5429571b@jacob-builder>
On Mon, Oct 14, 2019 at 10:14:05AM -0700, Jacob Pan wrote:
> Hi Joerg,
>
> Just another gentle reminder. I think we have reached consensus in this
> common code. Jean and Eric can confirm.
Yes for the whole series
Reviewed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-10-15 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 19:42 [PATCH v4 0/4] User API for nested shared virtual address (SVA) Jacob Pan
2019-10-02 19:42 ` [PATCH v4 1/4] iommu: Introduce cache_invalidate API Jacob Pan
2019-10-02 19:42 ` [PATCH v4 2/4] iommu: Add I/O ASID allocator Jacob Pan
2019-10-02 19:42 ` [PATCH v4 3/4] iommu/ioasid: Add custom allocators Jacob Pan
2019-10-04 17:18 ` Jean-Philippe Brucker
2019-10-02 19:42 ` [PATCH v4 4/4] iommu: Introduce guest PASID bind function Jacob Pan
2019-10-07 19:39 ` [PATCH v4 0/4] User API for nested shared virtual address (SVA) Jacob Pan
2019-10-14 17:14 ` Jacob Pan
2019-10-15 7:56 ` Jean-Philippe Brucker [this message]
2019-10-15 8:35 ` Auger Eric
2019-10-15 11:35 ` 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=20191015075641.GC1467695@lophozonia \
--to=jean-philippe@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.com \
--cc=jic23@kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.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).