From: Blue Swirl <blauwirbel@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RESEND 0/4] xen: misc fixes.
Date: Sat, 13 Jun 2009 16:41:19 +0300 [thread overview]
Message-ID: <f43fc5580906130641h2e262499sba71ee2f534b5fde@mail.gmail.com> (raw)
In-Reply-To: <1244712771-14432-1-git-send-email-kraxel@redhat.com>
On 6/11/09, Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
> This patch series is a collection of bugfixes for the xen backend
> drivers.
>
> Can also be pulled from
> git://git.et.redhat.com/qemu-kraxel.git (branch xen.v1).
>
> please apply,
Thanks, applied.
prev parent reply other threads:[~2009-06-13 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:32 [Qemu-devel] [PATCH RESEND 0/4] xen: misc fixes Gerd Hoffmann
2009-06-11 9:32 ` [Qemu-devel] [PATCH RESEND 1/4] xen_disk: move sanity check to the correct place Gerd Hoffmann
2009-06-11 9:32 ` [Qemu-devel] [PATCH RESEND 2/4] xen: adapt to qemu_machine changes Gerd Hoffmann
2009-06-11 9:32 ` [Qemu-devel] [PATCH RESEND 3/4] include inttypes.h in xen.h Gerd Hoffmann
2009-06-11 9:32 ` [Qemu-devel] [PATCH RESEND 4/4] xen nic: check tx queue after connect Gerd Hoffmann
2009-06-13 13:41 ` 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=f43fc5580906130641h2e262499sba71ee2f534b5fde@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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).