From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/5] Improve consistency of pci-ids.txt, use symbolic constants for QEMU devices
Date: Thu, 13 Dec 2012 10:19:33 +0100 [thread overview]
Message-ID: <1355390378-16692-1-git-send-email-pbonzini@redhat.com> (raw)
Five small, boring patches. Inspired by Gerd's patch at
http://lists.gnu.org/archive/html/qemu-devel/2012-10/msg05229.html which
unfortunately is already out of date.
Paolo Bonzini (5):
docs: move pci-ids.txt to docs/specs/
reorganize pci-ids.txt
virtio-9p: use symbolic constant, add to pci-ids.txt
ivshmem: use symbolic constant for PCI ID, add to pci-ids.txt
pci: use constants for devices under the 1B36 device ID, document them
docs/specs/pci-ids.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++
hw/9pfs/virtio-9p-device.c | 2 +-
hw/ivshmem.c | 7 +++++--
hw/pci.h | 8 ++++++++
hw/pci_bridge_dev.c | 8 ++------
hw/serial-pci.c | 12 +++++------
pci-ids.txt | 31 ----------------------------
7 files changed, 72 insertions(+), 46 deletions(-)
create mode 100644 docs/specs/pci-ids.txt
delete mode 100644 pci-ids.txt
--
1.8.0.1
next reply other threads:[~2012-12-13 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 9:19 Paolo Bonzini [this message]
2012-12-13 9:19 ` [Qemu-devel] [PATCH v2 1/5] docs: move pci-ids.txt to docs/specs/ Paolo Bonzini
2012-12-13 9:19 ` [Qemu-devel] [PATCH v2 2/5] reorganize pci-ids.txt Paolo Bonzini
2012-12-13 9:19 ` [Qemu-devel] [PATCH v2 3/5] virtio-9p: use symbolic constant, add to pci-ids.txt Paolo Bonzini
2012-12-13 9:19 ` [Qemu-devel] [PATCH v2 4/5] ivshmem: use symbolic constant for PCI ID, " Paolo Bonzini
2012-12-13 9:19 ` [Qemu-devel] [PATCH v2 5/5] pci: use constants for devices under the 1B36 device ID, document them Paolo Bonzini
2012-12-27 16:29 ` [Qemu-devel] [PATCH v2 0/5] Improve consistency of pci-ids.txt, use symbolic constants for QEMU devices Paolo Bonzini
2013-01-08 11:43 ` Paolo Bonzini
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=1355390378-16692-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=mst@redhat.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).