From: Gonglei <arei.gonglei@huawei.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [Question] about ipxe version update
Date: Thu, 4 Dec 2014 16:47:03 +0800 [thread overview]
Message-ID: <54801F87.3020602@huawei.com> (raw)
In-Reply-To: <1417680429.14168.112.camel@nilsson.home.kraxel.org>
On 2014/12/4 16:07, Gerd Hoffmann wrote:
> Hi,
>
>> When we tried the latest ipxe code, it's ok.
>> By git bisect, I found the patch of ipxe.git solved this problem.
>>
>> # git show 9f0b7f428af04d0c5ddda78f9b034625f2f91831
>> Author: Michael Brown <mcb30@ipxe.org>
>> Date: Sun Jun 1 19:24:16 2014 +0100
>
>> I noticed that the latest ipxe version in qemu is 2014.5.15, and was included
>> in Qemu-2.1 release version.
>>
>> commit d880b28cef4a8b4bc489a5caec201d019b9c0add
>> Author: Gerd Hoffmann <kraxel@redhat.com>
>> Date: Thu May 15 14:23:59 2014 +0200
>>
>> ipxe: update to current git
>>
>> Now that ipxe has separate settings for load / boot banner timeouts
>> re-enable the boot banner while keeping the load banner turned off,
>> so we don't add a delay to non-pxe boots.
>>
>> Does we have a plan to update ipxe version in QEMU? Thanks.
>
> Picking up a bugfix is a pretty good reason to update ...
>
>> I know QEMU 2.2 will be released tomorrow, December 5th.
>> Maybe we can't catch up with that.
>
> ... but not one day before the release. We can do the update early in
> 2.3 though, and maybe cherry-pick for 2.2.1 after it got some testing.
>
> cheers,
> Gerd
>
>
Got it, thanks!
Regards,
-Gonglei
prev parent reply other threads:[~2014-12-04 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 7:23 [Qemu-devel] [Question] about ipxe version update Gonglei (Arei)
2014-12-04 8:07 ` Gerd Hoffmann
2014-12-04 8:47 ` Gonglei [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=54801F87.3020602@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=weidong.huang@huawei.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).