From: "Xu, Quan" <quan.xu@intel.com>
To: Jan Beulich <JBeulich@suse.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
"Wu, Feng" <feng.wu@intel.com>
Subject: Re: [PATCH v4 0/2] Make the pcidevs_lock a recursive one
Date: Thu, 17 Mar 2016 01:39:03 +0000 [thread overview]
Message-ID: <945CA011AD5F084CBEA3E851C0AB28894B865DA0@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <56E9474102000078000DD087@prv-mh.provo.novell.com>
On March 16, 2016 6:45pm, <JBeulich@suse.com> wrote:
> >>> On 16.03.16 at 09:39, <dario.faggioli@citrix.com> wrote:
> > On Wed, 2016-03-16 at 02:39 +0000, Xu, Quan wrote:
> Quan - before sending such pings, please be sure to actually check the staging
> branch. And generally Dario is right - if anything, you should have pinged
> Suravee for his missing ack, and not everyone (i.e. the list).
>
Yes, you are right. I will follow it.
Before I send out pings, I have checked it on the http://xenbits.xen.org/gitweb/?p=xen.git;a=summary,
and I can't find this patch set.
Quan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-17 1:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 14:10 [PATCH v4 0/2] Make the pcidevs_lock a recursive one Quan Xu
2016-03-10 14:10 ` [PATCH v4 1/2] IOMMU/spinlock: Fix a bug found in AMD IOMMU initialization Quan Xu
2016-03-11 0:24 ` Tian, Kevin
2016-03-11 1:40 ` Xu, Quan
2016-03-10 14:10 ` [PATCH v4 2/2] IOMMU/spinlock: Make the pcidevs_lock a recursive one Quan Xu
2016-03-10 14:32 ` Jan Beulich
2016-03-10 14:38 ` Dario Faggioli
2016-03-11 1:38 ` Xu, Quan
2016-03-11 1:33 ` Xu, Quan
2016-03-16 2:39 ` [PATCH v4 0/2] " Xu, Quan
2016-03-16 8:39 ` Dario Faggioli
2016-03-16 10:45 ` Jan Beulich
2016-03-17 1:39 ` Xu, Quan [this message]
2016-03-17 2:07 ` Dario Faggioli
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=945CA011AD5F084CBEA3E851C0AB28894B865DA0@SHSMSX101.ccr.corp.intel.com \
--to=quan.xu@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=feng.wu@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.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).