From: Blue Swirl <blauwirbel@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL] qemu: pci fix
Date: Sat, 13 Feb 2010 09:05:55 +0200 [thread overview]
Message-ID: <f43fc5581002122305t6185de8fr434f178ca12559dd@mail.gmail.com> (raw)
In-Reply-To: <20100209113934.GA31975@redhat.com>
Thanks, pulled.
On Tue, Feb 9, 2010 at 1:39 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> The following changes since commit e8105ebb94bf8c79c8ee8a66df5e8dfaabbfdbe1:
> Paolo Bonzini (1):
> vl.c: avoid preprocessor directives in a printf call
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
>
> Isaku Yamahata (1):
> pci: fix pci_find_bus()
>
> hw/pci.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>
>
prev parent reply other threads:[~2010-02-13 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 11:39 [Qemu-devel] [PULL] qemu: pci fix Michael S. Tsirkin
2010-02-13 7:05 ` Blue Swirl [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=f43fc5581002122305t6185de8fr434f178ca12559dd@mail.gmail.com \
--to=blauwirbel@gmail.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).