From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH V2 00/10] various pci clean ups.
Date: Tue, 15 Dec 2009 13:41:19 +0200 [thread overview]
Message-ID: <20091215114119.GA16240@redhat.com> (raw)
In-Reply-To: <1260876367-28197-1-git-send-email-yamahata@valinux.co.jp>
On Tue, Dec 15, 2009 at 08:25:57PM +0900, Isaku Yamahata wrote:
> This patch series is for various somewhat atrandom clean up.
>
> - the patch "piix_pci: define symbolic value for PAM0, PAM6 and SMRAM."
> doesn't cause binary difference.
> I checked the piix_pci.o binary doesn't changed with the patch applied
> or not by diffing results of disassembling object files.
>
> - rebased to MST's git tree
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git pci.
> Anyway the only patch "pci: use pci_regs.h" 4 patch conflicts.
> So I expect all but the patch "pci: use pci_regs.h" can applies to
> unstable tree. And it's trivial to resolve the conflict.
>
> changes v1 -> v2:
> - dropped the patch "pci: clean up pci_bar_address()"
> - reordered
> - rebased to git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git pci
> - updated I440FX patch.
> - added link to I440FX link
Thanks!
Applied.
> Isaku Yamahata (10):
> pci: remove PCIBus::config_reg.
> pci: s/PCI_SUBVENDOR_ID/PCI_SUBSYSTEM_VENDOR_ID/g
> pci: import Linux pci_regs.h
> pci: use pci_regs.h
> gt64xxx: remove gt64120_{read, write}_config().
> acpi: use range helper function.
> msix: use range helper function.
> piix_pci: define symbolic value for PAM0, PAM6 and SMRAM.
> piix_pci: use range helper function
> piix_pci: add link to i440fx data sheet.
>
> hw/acpi.c | 2 +-
> hw/gt64xxx.c | 13 +-
> hw/msix.c | 2 +-
> hw/pci.c | 3 +-
> hw/pci.h | 77 +-------
> hw/pci_regs.h | 665 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/piix_pci.c | 22 ++-
> 7 files changed, 689 insertions(+), 95 deletions(-)
> create mode 100644 hw/pci_regs.h
prev parent reply other threads:[~2009-12-15 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 11:25 [Qemu-devel] [PATCH V2 00/10] various pci clean ups Isaku Yamahata
2009-12-15 11:25 ` [Qemu-devel] [PATCH V2 01/10] pci: remove PCIBus::config_reg Isaku Yamahata
2009-12-15 11:25 ` [Qemu-devel] [PATCH V2 02/10] pci: s/PCI_SUBVENDOR_ID/PCI_SUBSYSTEM_VENDOR_ID/g Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 03/10] pci: import Linux pci_regs.h Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 04/10] pci: use pci_regs.h Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 05/10] gt64xxx: remove gt64120_{read, write}_config() Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 06/10] acpi: use range helper function Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 07/10] msix: " Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 08/10] piix_pci: define symbolic value for PAM0, PAM6 and SMRAM Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 09/10] piix_pci: use range helper function Isaku Yamahata
2009-12-15 11:26 ` [Qemu-devel] [PATCH V2 10/10] piix_pci: add link to i440fx data sheet Isaku Yamahata
2009-12-15 11:41 ` Michael S. Tsirkin [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=20091215114119.GA16240@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).