From: Anthony Liguori <aliguori@us.ibm.com>
To: Jordan Justen <jljusten@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Last Call for 1.5 before Hard Freeze
Date: Mon, 06 May 2013 15:31:19 -0500 [thread overview]
Message-ID: <87r4hj4zqg.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFe8ug_SoVd9tFOaNoTf+vEb=tPTuYRv320YbjLa4XFcFSUr1g@mail.gmail.com>
Jordan Justen <jljusten@gmail.com> writes:
> On Mon, May 6, 2013 at 7:42 AM, Anthony Liguori <aliguori@us.ibm.com> wrote:
>> I believe I have processed all of the outstanding pull requests and
>> patches tagged for 1.5. If there are any other patches or pull requests
>> you would like to be considered, please respond to this note with a
>> pointer to the patch or make sure you send it out tagged with 'for-1.5'
>> no later than 5pm US/Eastern.
>
> Is there a chance of including the KVM PC flash series in 1.5?
> Unfortunately, I'm assuming no given the timing.
I think we're going to need to delay it. Did we ever come to a
consensus about what to do on older kernels?
Regards,
Anthony Liguori
>
> It does seem less than ideal to have -pflash go from working on qemu
> 1.2-1.4, to silently being ignored in 1.5, and then working again in
> 1.6...
>
> -Jordan
next prev parent reply other threads:[~2013-05-06 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 14:42 [Qemu-devel] Last Call for 1.5 before Hard Freeze Anthony Liguori
2013-05-06 16:37 ` Paolo Bonzini
2013-05-06 18:08 ` Anthony Liguori
2013-05-07 6:35 ` Gerd Hoffmann
2013-05-06 18:10 ` Michael Tokarev
2013-05-06 20:12 ` Jordan Justen
2013-05-06 20:31 ` Anthony Liguori [this message]
2013-05-06 20:41 ` Paolo Bonzini
2013-05-06 21:07 ` Jordan Justen
2013-05-07 4:40 ` Paolo Bonzini
2013-05-06 21:21 ` Jordan Justen
2013-05-06 20:45 ` Andreas Färber
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=87r4hj4zqg.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=jljusten@gmail.com \
--cc=pbonzini@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).