From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL v1 0/2] Merge qcrypto 2017/02/27
Date: Mon, 27 Feb 2017 13:39:25 +0000 [thread overview]
Message-ID: <20170227133927.759-1-berrange@redhat.com> (raw)
The following changes since commit d992f2f1368ceb92e6bfd8efece174110f4236ff:
Merge remote-tracking branch 'remotes/artyom/tags/pull-sun4v-20170226' into staging (2017-02-26 22:40:23 +0000)
are available in the git repository at:
git://github.com/berrange/qemu tags/pull-qcrypto-2017-02-27-1
for you to fetch changes up to 32c813e6c2a857b93b897901b7e20281397528a3:
crypto: assert cipher algorithm is always valid (2017-02-27 13:37:14 +0000)
----------------------------------------------------------------
Merge qcrypto 2017/02/27 v1
----------------------------------------------------------------
Li Qiang (1):
crypto: fix leak in ivgen essiv init
Prasad J Pandit (1):
crypto: assert cipher algorithm is always valid
crypto/cipher.c | 8 ++------
crypto/ivgen-essiv.c | 1 +
2 files changed, 3 insertions(+), 6 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-27 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 13:39 Daniel P. Berrange [this message]
2017-02-27 13:39 ` [Qemu-devel] [PULL v1 1/2] crypto: fix leak in ivgen essiv init Daniel P. Berrange
2017-02-27 13:39 ` [Qemu-devel] [PULL v1 2/2] crypto: assert cipher algorithm is always valid Daniel P. Berrange
2017-02-27 16:30 ` [Qemu-devel] [PULL v1 0/2] Merge qcrypto 2017/02/27 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=20170227133927.759-1-berrange@redhat.com \
--to=berrange@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.