From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<konrad.wilk@oracle.com>, <stefano.stabellini@eu.citrix.com>
Cc: <linux-kernel@vger.kernel.org>, <jun.nakajima@intel.com>,
<xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH v4 0/2] xen/pci: Use APIC for MSIs when APIC virtualization is supported
Date: Thu, 4 Dec 2014 13:44:06 +0000 [thread overview]
Message-ID: <54806526.7040906@citrix.com> (raw)
In-Reply-To: <54803DF7.1030903@citrix.com>
On 04/12/14 10:56, David Vrabel wrote:
> On 02/12/14 20:19, Boris Ostrovsky wrote:
>> Changes in v4:
>> * Added comment describing what we check for in pci_xen_init()
>
> I applied v3 ages ago to the devel/for-linus-3.19 branch and I'm not
> going to mess about replacing it for a comment change.
I had to mess with it anyway to fix a build problem. I've applied this
version.
Thanks.
David
next prev parent reply other threads:[~2014-12-04 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 20:19 [PATCH v4 0/2] xen/pci: Use APIC for MSIs when APIC virtualization is supported Boris Ostrovsky
2014-12-02 20:19 ` [PATCH v4 1/2] xen/pci: Defer initialization of MSI ops on HVM guests until after x2APIC has been set up Boris Ostrovsky
2014-12-02 20:19 ` Boris Ostrovsky
2014-12-02 20:19 ` [PATCH v4 2/2] xen/pci: Use APIC directly when APIC virtualization is supported by hardware Boris Ostrovsky
2014-12-02 20:19 ` Boris Ostrovsky
2014-12-02 20:48 ` [PATCH v4 0/2] xen/pci: Use APIC for MSIs when APIC virtualization is supported Konrad Rzeszutek Wilk
2014-12-02 20:48 ` Konrad Rzeszutek Wilk
2014-12-03 0:10 ` [Xen-devel] " Andrew Cooper
2014-12-03 0:10 ` Andrew Cooper
2014-12-04 10:56 ` David Vrabel
2014-12-04 10:56 ` [Xen-devel] " David Vrabel
2014-12-04 13:44 ` David Vrabel [this message]
2014-12-04 13:44 ` David Vrabel
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=54806526.7040906@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jun.nakajima@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.