From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
markmc@redhat.com, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
kraxel@redhat.com, Avi Kivity <avi@redhat.com>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: qemu: tree for pci related fixes
Date: Wed, 23 Sep 2009 13:11:48 -0500 [thread overview]
Message-ID: <4ABA64E4.7070007@codemonkey.ws> (raw)
In-Reply-To: <20090923155559.GA18203@redhat.com>
Hi Michael,
Michael S. Tsirkin wrote:
> Hi!
> I created a qemu tree to collect pci related qemu fixes,
> to make sure they don't get lost.
>
> The idea's the patches have been posted on list already, so it should be enough
> to repost a short summary here, rather than flood everyone's
> mailboxes by reposting a full patchset.
>
> The tree is here:
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git pci
>
> Beware: do not publish a tree on top of this one as I might be rebasing it. If
> you want me to add a patch there, just mail me.
>
> Below's the first nag:
>
> ---
>
> Here are the pci fixes I know of that haven't been applied already.
> Anthony, all, any more comments on any of them?
> If yes, please reply on the original patch.
> If no, please apply.
>
> 9305505 qemu/virtio-pci: remove unnecessary check
>
This was posted yesterday.
> 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
>
These were posted a week ago. I am behind on staging unfortunately.
I think it makes sense for everyone to keep their own trees and to make
them publicly accessible. However, for resends, I would still like them
to occur on the mailing list.
In general, I would wait at least two weeks for a resend. I understand
that this is a very long time and I'm working on trying to make patch
response time more reliable. I would like to point out though that
these patches are by no means lost.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-09-23 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 15:56 [Qemu-devel] qemu: tree for pci related fixes Michael S. Tsirkin
2009-09-23 18:11 ` Anthony Liguori [this message]
2009-09-23 19:38 ` [Qemu-devel] " Michael S. Tsirkin
2009-09-23 20:38 ` Anthony Liguori
2009-09-24 4:18 ` Michael S. Tsirkin
2009-09-24 6:38 ` Avi Kivity
2009-09-24 4:41 ` 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=4ABA64E4.7070007@codemonkey.ws \
--to=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=mst@redhat.com \
--cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.