From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org, Carsten Otte <cotte@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
kraxel@redhat.com, markmc@redhat.com,
Anthony Liguori <anthony@codemonkey.ws>,
Isaku Yamahata <yamahata@valinux.co.jp>
Subject: [Qemu-devel] what's on qemu tree for pci related fixes
Date: Mon, 5 Oct 2009 16:51:15 +0200 [thread overview]
Message-ID: <20091005145115.GA31281@redhat.com> (raw)
Here's the list of patches on my pci fixes tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git pci
Here are the pci fixes I know of that haven't been applied already.
All, any more comments on any of them?
If yes, please reply on the original patch, not here.
eee1bff qemu: clean up target page usage in msix
52a5bce fix comment on cpu_register_physical_memory_offset
9305505 qemu/virtio-pci: remove unnecessary check
c128c88 qemu/pci: reset device registers on bus reset
74b7e8b qemu/pci: refactor code/symbolic constants
5307502 qemu/virtio: fix reset with device removal
c1f2e99 qemu/qdev: type safety in reset handler
Isaku Yamahata, would you like me to put some of the fixes you posted
onto this tree, to reduce the chance if conflict? I can do this, but
you'll have to start including changelog when you repost your patches so
I can figure out that some patch was not changed.
Anthony, I decided not to rebase the tree, I'll merge master in,
instead, on the off chance that you finally get converted to using git
pull. But if this makes things inconvenient for you, pls let me know:
maybe I can keep both a rebased and non-rebased branches around.
Thanks,
--
MST
next reply other threads:[~2009-10-05 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 14:51 Michael S. Tsirkin [this message]
2009-10-05 15:45 ` [Qemu-devel] Re: what's on qemu tree for pci related fixes Anthony Liguori
2009-10-05 20:24 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-11-22 15:19 [Qemu-devel] " Michael S. Tsirkin
2009-11-30 10:48 Michael S. Tsirkin
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=20091005145115.GA31281@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=markmc@redhat.com \
--cc=paul@codesourcery.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).