From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [v2] Define PCI vendor and device IDs in pci.h
Date: Mon, 26 Jan 2009 09:38:57 -0600 [thread overview]
Message-ID: <497DD911.9050009@us.ibm.com> (raw)
In-Reply-To: <20090124165342.GA29800@miranda.arrow>
Stuart Brady wrote:
> This patch defines PCI vendor and device IDs in pci.h (matching those
> from Linux's pci_ids.h), and uses those definitions where appropriate.
>
> Change from v1:
> Introduces pci_config_set_vendor_id() / pci_config_set_device_id()
> accessors as suggested by Anthony Liguori.
>
> Signed-off-by: Stuart Brady <stuart.brady@gmail.com>
>
Applied. Thanks.
If anyone is looking for a janitor-type job, adding more config
accessors and adding defines for class-types, devices, etc. it would go
a long way to making a lot of that code more readable.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-01-26 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 16:53 [Qemu-devel] [PATCH] [v2] Define PCI vendor and device IDs in pci.h Stuart Brady
2009-01-26 15:38 ` 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=497DD911.9050009@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).