From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
ashok.raj@intel.com, sanjay.k.kumar@intel.com,
jacob.jun.pan@intel.com, kevin.tian@intel.com,
yi.l.liu@intel.com, yi.y.sun@intel.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/9] iommu/vt-d: Improve PASID id and table management
Date: Sat, 7 Jul 2018 11:22:34 +0800 [thread overview]
Message-ID: <5B4031FA.6000706@linux.intel.com> (raw)
In-Reply-To: <20180706123155.oyubygktu3q3banv@8bytes.org>
Hi Joerg,
On 07/06/2018 08:31 PM, Joerg Roedel wrote:
> Hey Lu,
>
> the patches do not apply cleanly to my x86/vt-d branch. Can you rebase
> against that branch after the weekend when I pushed it out and re-send,
> please?
Sure.
Best regards,
Lu Baolu
prev parent reply other threads:[~2018-07-07 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 5:17 [PATCH v3 0/9] iommu/vt-d: Improve PASID id and table management Lu Baolu
2018-06-19 5:17 ` [PATCH v3 1/9] iommu/vt-d: Global PASID name space Lu Baolu
2018-06-19 5:17 ` [PATCH v3 2/9] iommu/vt-d: Avoid using idr_for_each_entry() Lu Baolu
2018-06-19 5:17 ` [PATCH v3 3/9] iommu/vt-d: Apply global PASID in SVA Lu Baolu
2018-06-19 5:17 ` [PATCH v3 4/9] iommu/vt-d: Move device_domain_info to header Lu Baolu
2018-06-19 5:17 ` [PATCH v3 5/9] iommu/vt-d: Add for_each_device_domain() helper Lu Baolu
2018-06-19 5:17 ` [PATCH v3 6/9] iommu/vt-d: Per PCI device pasid table interfaces Lu Baolu
2018-06-19 5:17 ` [PATCH v3 7/9] iommu/vt-d: Allocate and free pasid table Lu Baolu
2018-06-19 5:17 ` [PATCH v3 8/9] iommu/vt-d: Apply per pci device pasid table in SVA Lu Baolu
2018-06-19 5:17 ` [PATCH v3 9/9] iommu/vt-d: Remove the obsolete per iommu pasid tables Lu Baolu
2018-07-06 12:31 ` [PATCH v3 0/9] iommu/vt-d: Improve PASID id and table management Joerg Roedel
2018-07-07 3:22 ` Lu Baolu [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=5B4031FA.6000706@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjay.k.kumar@intel.com \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@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