From: Alex Williamson <alex.williamson@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] qemu: Update Linux headers
Date: Mon, 15 Oct 2012 15:04:57 -0600 [thread overview]
Message-ID: <1350335097.2112.175.camel@bling.home> (raw)
In-Reply-To: <87vcebwj5v.fsf@codemonkey.ws>
On Mon, 2012-10-15 at 15:54 -0500, Anthony Liguori wrote:
> Alex Williamson <alex.williamson@redhat.com> writes:
>
> > Based on v3.7-rc1-3-g29bb4cc
>
> Normally this would go through qemu-kvm/uq/master but since this is from
> Linus' tree, it's less of a concern.
>
> Nonetheless, I'd prefer we did it from v3.7-rc1 instead of a random git
> snapshot.
Resent against v3.7-rc1, which ends up just being a changelog change, no
header changes since rc1. Thanks,
Alex
prev parent reply other threads:[~2012-10-15 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 20:15 [Qemu-devel] [PATCH] qemu: Update Linux headers Alex Williamson
2012-10-15 20:54 ` Anthony Liguori
2012-10-15 21:04 ` Alex Williamson [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=1350335097.2112.175.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--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).