Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv3] qemu: Upgrade to 2.7.1
Date: Sun, 22 Jan 2017 12:33:57 +0100	[thread overview]
Message-ID: <1485084837.20333.4.camel@intel.com> (raw)
In-Reply-To: <1484950557-27915-1-git-send-email-anibal.limon@linux.intel.com>

On Fri, 2017-01-20 at 16:15 -0600, Aníbal Limón wrote:
> Minor upgrade contains fixes from 2.7.0.
> 
> Removed patches (already in upstream):
[...]
> diff --git a/meta/recipes-devtools/qemu/qemu_2.7.0.bb b/meta/recipes-devtools/qemu/qemu_2.7.1.bb
> similarity index 66%
> rename from meta/recipes-devtools/qemu/qemu_2.7.0.bb
> rename to meta/recipes-devtools/qemu/qemu_2.7.1.bb
> index 0d680a7..8180c5f 100644
> --- a/meta/recipes-devtools/qemu/qemu_2.7.0.bb
> +++ b/meta/recipes-devtools/qemu/qemu_2.7.1.bb
> @@ -9,16 +9,14 @@ SRC_URI += "file://configure-fix-Darwin-target-detection.patch \
>              file://no-valgrind.patch \
>              file://pathlimit.patch \
>              file://qemu-2.5.0-cflags.patch \
> -            file://0001-virtio-zero-vq-inuse-in-virtio_reset.patch \
> -            file://0002-fix-CVE-2016-7423.patch \
>              file://0003-fix-CVE-2016-7908.patch \
>              file://0004-fix-CVE-2016-7909.patch \
> -            file://0001-pci-assign-sync-MSI-MSI-X-cap-and-table-with-PCIDevi.patch \
>  "
>  
> -SRC_URI_prepend = "http://wiki.qemu-project.org/download/${BP}.tar.bz2"
> -SRC_URI[md5sum] = "08d4d06d1cb598efecd796137f4844ab"
> -SRC_URI[sha256sum] = "326e739506ba690daf69fc17bd3913a6c313d9928d743bd8eddb82f403f81e53"
> +SRC_URI =+ "http://wiki.qemu-project.org/download/${BP}.tar.bz2"
> +
> +SRC_URI[md5sum] = "a315bc51ed443a08d2cf1416d76b9ab4"
> +SRC_URI[sha256sum] = "68636788eb69bcb0b44ba220b32b50495d6bd5712a934c282217831c4822958f"

Looks good to me, thanks.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





      reply	other threads:[~2017-01-22 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 22:15 [PATCHv3] qemu: Upgrade to 2.7.1 Aníbal Limón
2017-01-22 11:33 ` Patrick Ohly [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=1485084837.20333.4.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=anibal.limon@linux.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