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-next 2016/07/20
Date: Wed, 20 Jul 2016 12:32:52 +0100 [thread overview]
Message-ID: <1469014374-6731-1-git-send-email-berrange@redhat.com> (raw)
The following changes since commit a3b343772114c8c98986508f3352a631164f913c:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2016-07-19 15:08:05 +0100)
are available in the git repository at:
git://github.com/berrange/qemu tags/pull-qcrypto-2016-07-20-1
for you to fetch changes up to 718083de8051736bba02f10dc4a88bd14ff6b79b:
crypto: don't open-code qcrypto_hash_supports (2016-07-19 16:46:23 +0100)
----------------------------------------------------------------
Merge qcrypto-next 2016/07/20 v1
----------------------------------------------------------------
Daniel P. Berrange (2):
crypto: use glib as fallback for hash algorithm
crypto: don't open-code qcrypto_hash_supports
crypto/Makefile.objs | 2 +-
crypto/hash-gcrypt.c | 3 +-
crypto/hash-glib.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++++
crypto/hash-nettle.c | 3 +-
crypto/hash-stub.c | 41 -----------------------
5 files changed, 96 insertions(+), 46 deletions(-)
create mode 100644 crypto/hash-glib.c
delete mode 100644 crypto/hash-stub.c
--
2.7.4
next reply other threads:[~2016-07-20 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 11:32 Daniel P. Berrange [this message]
2016-07-20 11:32 ` [Qemu-devel] [PULL v1 1/2] crypto: use glib as fallback for hash algorithm Daniel P. Berrange
2016-07-20 11:32 ` [Qemu-devel] [PULL v1 2/2] crypto: don't open-code qcrypto_hash_supports Daniel P. Berrange
2016-07-20 19:31 ` [Qemu-devel] [PULL v1 0/2] Merge qcrypto-next 2016/07/20 Peter Maydell
2016-07-21 9:43 ` Daniel P. Berrange
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=1469014374-6731-1-git-send-email-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.