From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu: security bump to 2.12.1
Date: Mon, 8 Oct 2018 17:46:33 +0200 [thread overview]
Message-ID: <20181008174633.289720b4@windsurf> (raw)
In-Reply-To: <20181008070842.25883-1-peter@korsgaard.com>
Hello,
On Mon, 8 Oct 2018 09:08:42 +0200, Peter Korsgaard wrote:
> From the release notes:
>
> This update contains new mitigation functionality for CVE-2018-3639
> (Speculative Store Bypass) in x86. There are also bug fixes for
> migration, Intel IOMMU emulation, block layer/image handling, ARM
> emulation, and various other areas.
>
> https://www.mail-archive.com/qemu-devel at nongnu.org/msg553574.html
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/qemu/qemu.hash | 2 +-
> package/qemu/qemu.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-08 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 7:08 [Buildroot] [PATCH] qemu: security bump to 2.12.1 Peter Korsgaard
2018-10-08 15:46 ` Thomas Petazzoni [this message]
2018-10-21 9:25 ` Peter Korsgaard
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=20181008174633.289720b4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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