From: Randy MacLeod <randy.macleod@windriver.com>
To: Wang Xin <wangxin2015.fnst@cn.fujitsu.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu: 2.6.0 -> 2.6.1
Date: Wed, 7 Sep 2016 23:32:56 -0400 [thread overview]
Message-ID: <5f29e025-2aff-fdc4-c4fd-c9b17abd20e2@windriver.com> (raw)
In-Reply-To: <1472291503-1650-1-git-send-email-wangxin2015.fnst@cn.fujitsu.com>
On 2016-08-27 05:51 AM, Wang Xin wrote:
> Upgrade qemu from 2.6.0 to 2.6.1.
Not merged yet even in master-next.
Hmmm, 2.7.0 is also available as of Sept 2nd.
It's too late for oe-core-2.2 - right?
The Changelog is interesting:
http://wiki.qemu.org/ChangeLog/2.7
and here are a couple of shorter summaries from (ugh) Phoronix :
https://www.phoronix.com/scan.php?page=news_item&px=QEMU-2.7-Released
http://www.phoronix.com/scan.php?page=news_item&px=QEMU-2.7-RC0
Shiny! :)
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada, K2K 2W5
next prev parent reply other threads:[~2016-09-08 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 9:51 [PATCH] qemu: 2.6.0 -> 2.6.1 Wang Xin
2016-09-08 3:32 ` Randy MacLeod [this message]
2016-09-08 8:40 ` Richard Purdie
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=5f29e025-2aff-fdc4-c4fd-c9b17abd20e2@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangxin2015.fnst@cn.fujitsu.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