From: Isaku Yamahata <yamahata@valinux.co.jp>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH 00/04] RFC: pci bridge clean up and multiple pci bus support.
Date: Fri, 1 May 2009 18:33:52 +0900 [thread overview]
Message-ID: <1241170436-2800-1-git-send-email-yamahata@valinux.co.jp> (raw)
Although I haven't finished this work, people seems to be
interested in pci bridge emultion and multiple pci bus support.
So I decided to send out these patches to avoid duplicated work.
Please comment on pci bridge emulation and multiple pci bus support.
I'm aware of Markus's work and I'm willing to help it.
Eventually those patches will be integrated.
thanks,
next reply other threads:[~2009-05-01 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 9:33 Isaku Yamahata [this message]
2009-05-01 9:33 ` [Qemu-devel] [PATCH] minor fix of pci_register_bus() Isaku Yamahata
2009-05-01 9:33 ` [Qemu-devel] [PATCH] use PCI_HEADER_TYPE Isaku Yamahata
2009-05-01 9:33 ` [Qemu-devel] [PATCH] pci bus: preliminary for multi pci bus support Isaku Yamahata
2009-05-01 9:33 ` [Qemu-devel] [PATCH] try to implement complete pci-to-pci bridge emulator Isaku Yamahata
2009-05-01 14:17 ` M. Warner Losh
2009-05-04 16:06 ` Isaku Yamahata
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=1241170436-2800-1-git-send-email-yamahata@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=armbru@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).