From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add and use remaining #defines for PCI device IDs
Date: Fri, 13 Mar 2009 10:31:32 -0500 [thread overview]
Message-ID: <49BA7C54.6080207@us.ibm.com> (raw)
In-Reply-To: <20090307211959.GA11120@miranda.arrow>
Stuart Brady wrote:
> This patch adds and uses #defines for the remaining hardcoded PCI
> device IDs. It also moves definitions taken from linux/pci_ids.h
> into a separate header (hw/pci_ids.h), removes the 'RTL' from
> PCI_DEVICE_ID_REALTEK_RTL8029, and renames PCI_DEVICE_ID_FSL_E500
> to PCI_DEVICE_ID_MPC8533E to match Linux's definition.
>
> Changes in v2:
> * Don't use C99-style comments
> * Move definitions from linux/pci_ids.h into a separate header
> * Rename PCI_DEVICE_ID_FSL_E500 to PCI_DEVICE_ID_MPC8533E
>
> Signed-off-by: Stuart Brady <stuart.brady@gmail.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-03-13 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 21:19 [Qemu-devel] [PATCH v2] Add and use remaining #defines for PCI device IDs Stuart Brady
2009-03-13 15:31 ` Anthony Liguori [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=49BA7C54.6080207@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.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).