From: Saul Wold <sgw@linux.intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemu: upgrade to 1.3.1
Date: Mon, 11 Feb 2013 09:46:36 -0800 [thread overview]
Message-ID: <51192E7C.5010400@linux.intel.com> (raw)
In-Reply-To: <1360587708-5044-1-git-send-email-constantinx.musca@intel.com>
qhat kind of testing have you done with this update, since qemu is core
to our BSPs I want to make sure we have tested it well.
Thanks
Sau!
On 02/11/2013 05:01 AM, Constantin Musca wrote:
> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
> ---
> meta/recipes-devtools/qemu/{qemu_1.3.0.bb => qemu_1.3.1.bb} | 4 ++--
> meta/recipes-devtools/qemu/qemu_git.bb | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-devtools/qemu/{qemu_1.3.0.bb => qemu_1.3.1.bb} (64%)
>
> diff --git a/meta/recipes-devtools/qemu/qemu_1.3.0.bb b/meta/recipes-devtools/qemu/qemu_1.3.1.bb
> similarity index 64%
> rename from meta/recipes-devtools/qemu/qemu_1.3.0.bb
> rename to meta/recipes-devtools/qemu/qemu_1.3.1.bb
> index 7d007ea..c04b2be 100644
> --- a/meta/recipes-devtools/qemu/qemu_1.3.0.bb
> +++ b/meta/recipes-devtools/qemu/qemu_1.3.1.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=441c28d2cf86e15a37fa47e15a72fbac \
> file://COPYING.LIB;endline=24;md5=c04def7ae38850e7d3ef548588159913"
>
> SRC_URI_prepend = "http://wiki.qemu.org/download/qemu-${PV}.tar.bz2"
> -SRC_URI[md5sum] = "a4030ddd2ba324152a97d65d3c0b247d"
> -SRC_URI[sha256sum] = "878055ec05bc28fecfe2da97eb8bc992e8635575b67cebdfc5ca1ede171140a8"
> +SRC_URI[md5sum] = "5dbc6c22f47efca71dfaae0dd80dcf9e"
> +SRC_URI[sha256sum] = "3772e7ef0c9b4178195edcf90e711f12ba123f465fcf09fb43b56bdacaca0eaf"
>
> PR = "r0"
> diff --git a/meta/recipes-devtools/qemu/qemu_git.bb b/meta/recipes-devtools/qemu/qemu_git.bb
> index 9465203..328e3bf 100644
> --- a/meta/recipes-devtools/qemu/qemu_git.bb
> +++ b/meta/recipes-devtools/qemu/qemu_git.bb
> @@ -1,6 +1,6 @@
> require qemu.inc
>
> -SRCREV = "6d6c9f59ca1b1a76ade7ad868bef191818f58819"
> +SRCREV = "04024dea2674861fcf13582a77b58130c67fccd8"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=441c28d2cf86e15a37fa47e15a72fbac \
> file://COPYING.LIB;endline=24;md5=c04def7ae38850e7d3ef548588159913"
>
next prev parent reply other threads:[~2013-02-11 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 13:01 [PATCH] qemu: upgrade to 1.3.1 Constantin Musca
2013-02-11 17:46 ` Saul Wold [this message]
2013-02-12 8:19 ` Constantin Musca
-- strict thread matches above, loose matches on Subject: below --
2013-02-13 7:46 [PATCH] qemu: Upgrade " Khem Raj
2013-02-13 18:44 ` Saul Wold
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=51192E7C.5010400@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=constantinx.musca@intel.com \
--cc=openembedded-core@lists.openembedded.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