From: Anthony PERARD <anthony.perard@citrix.com>
To: konrad@darnok.org
Cc: Xen Devel <xen-devel@lists.xensource.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH V8 RESEND 1/8] pci_ids: Add INTEL_82599_VF id.
Date: Mon, 14 May 2012 11:52:03 +0100 [thread overview]
Message-ID: <CAJJyHjKDYyffS9zB-xuNcadWw=c7fGgYLhe2AhGODsKAgErRoA@mail.gmail.com> (raw)
In-Reply-To: <CAPbh3ruY2npfORN-+oTt0i966RyzvCOBxnZ1x1OHbAj+ouLYcA@mail.gmail.com>
On Sat, May 12, 2012 at 2:43 AM, Konrad Rzeszutek Wilk
<konrad@darnok.org> wrote:
> On Mon, Mar 19, 2012 at 12:54 PM, Anthony PERARD
> <anthony.perard@citrix.com> wrote:
>> On 19/03/12 11:50, Stefano Stabellini wrote:
>>>
>>> On Fri, 16 Mar 2012, Anthony PERARD wrote:
>>>>
>>>> Signed-off-by: Anthony PERARD<anthony.perard@citrix.com>
>>>> ---
>>>> hw/pci_ids.h | 1 +
>>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/hw/pci_ids.h b/hw/pci_ids.h
>>>> index e8235a7..943106a 100644
>>>> --- a/hw/pci_ids.h
>>>> +++ b/hw/pci_ids.h
>>>> @@ -118,6 +118,7 @@
>>>> #define PCI_DEVICE_ID_INTEL_82801I_UHCI6 0x2939
>>>> #define PCI_DEVICE_ID_INTEL_82801I_EHCI1 0x293a
>>>> #define PCI_DEVICE_ID_INTEL_82801I_EHCI2 0x293c
>>>> +#define PCI_DEVICE_ID_INTEL_82599_VF 0x10ed
>>>
>>>
>>> maybe it should be PCI_DEVICE_ID_INTEL_82599_SFP_VF for consistency with
>>> Linux?
>>
>>
>> Ok, I'll change that.
>>
>
> And can you add why you need this?
Done in the V11.
--
Anthony PERARD
next prev parent reply other threads:[~2012-05-14 10:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 16:54 [PATCH V8 RESEND 0/8] Xen PCI Passthrough Anthony PERARD
2012-03-16 16:54 ` [PATCH V8 RESEND 1/8] pci_ids: Add INTEL_82599_VF id Anthony PERARD
2012-03-19 11:50 ` Stefano Stabellini
2012-03-19 16:54 ` Anthony PERARD
2012-05-12 1:43 ` Konrad Rzeszutek Wilk
2012-05-14 10:52 ` Anthony PERARD [this message]
2012-03-16 16:54 ` [PATCH V8 RESEND 2/8] configure: Introduce --enable-xen-pci-passthrough Anthony PERARD
2012-03-19 11:51 ` Stefano Stabellini
2012-05-12 1:42 ` Konrad Rzeszutek Wilk
2012-05-14 10:49 ` [Xen-devel] " Anthony PERARD
2012-05-16 11:15 ` Konrad Rzeszutek Wilk
2012-03-16 16:54 ` [PATCH V8 RESEND 3/8] Introduce HostPCIDevice to access a pci device on the host Anthony PERARD
2012-03-19 11:53 ` Stefano Stabellini
2012-03-16 16:54 ` [PATCH V8 RESEND 4/8] pci.c: Add pci_check_bar_overlap Anthony PERARD
2012-03-19 11:55 ` Stefano Stabellini
2012-03-19 13:15 ` Michael S. Tsirkin
2012-03-19 17:22 ` Anthony PERARD
2012-03-16 16:54 ` [PATCH V8 RESEND 5/8] Introduce Xen PCI Passthrough, qdevice (1/3) Anthony PERARD
2012-03-19 12:00 ` Stefano Stabellini
2012-05-12 1:53 ` Konrad Rzeszutek Wilk
2012-03-16 16:54 ` [PATCH V8 RESEND 6/8] Introduce Xen PCI Passthrough, PCI config space helpers (2/3) Anthony PERARD
2012-03-19 12:01 ` Stefano Stabellini
2012-03-16 16:54 ` [PATCH V8 RESEND 7/8] Introduce apic-msidef.h Anthony PERARD
2012-03-19 12:04 ` Stefano Stabellini
2012-03-16 16:54 ` [PATCH V8 RESEND 8/8] Introduce Xen PCI Passthrough, MSI (3/3) Anthony PERARD
2012-03-19 12:04 ` Stefano Stabellini
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='CAJJyHjKDYyffS9zB-xuNcadWw=c7fGgYLhe2AhGODsKAgErRoA@mail.gmail.com' \
--to=anthony.perard@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=konrad@darnok.org \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).