From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL for-2.4-rc0 0/2] Urgent fixes for 2.4
Date: Thu, 09 Jul 2015 17:19:21 +0200 [thread overview]
Message-ID: <559E90F9.3060909@de.ibm.com> (raw)
In-Reply-To: <1436453830-4700-1-git-send-email-pbonzini@redhat.com>
Am 09.07.2015 um 16:57 schrieb Paolo Bonzini:
> The following changes since commit acf7b7fdf31fa76b53803790917c8acf23a2badb:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2015-07-08 20:46:35 +0100)
>
> are available in the git repository at:
>
> git://github.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to 4f4f6976d80614e2d81cea4385885876f24bb257:
>
> crypto: fix builtin qcrypto_cipher_free (2015-07-09 16:53:45 +0200)
>
> ----------------------------------------------------------------
> Fixes for two bad bugs. For 2.4-rc0.
>
> ----------------------------------------------------------------
> Paolo Bonzini (2):
> migration: fix RCU deadlock
> crypto: fix builtin qcrypto_cipher_free
>
> crypto/cipher-builtin.c | 4 +++-
> migration/ram.c | 3 ++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
CC Peter missing?
next prev parent reply other threads:[~2015-07-09 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 14:57 [Qemu-devel] [PULL for-2.4-rc0 0/2] Urgent fixes for 2.4 Paolo Bonzini
2015-07-09 14:57 ` [Qemu-devel] [PULL 1/2] migration: fix RCU deadlock Paolo Bonzini
2015-07-09 14:57 ` [Qemu-devel] [PULL 2/2] crypto: fix builtin qcrypto_cipher_free Paolo Bonzini
2015-07-09 15:04 ` Aurelien Jarno
2015-07-09 15:19 ` Christian Borntraeger [this message]
2015-07-09 15:21 ` [Qemu-devel] [PULL for-2.4-rc0 0/2] Urgent fixes for 2.4 Peter Maydell
2015-07-09 16:28 ` Peter Maydell
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=559E90F9.3060909@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).