qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PULL v1 0/4] Merge qcrypto 2017/05/07
Date: Wed, 10 May 2017 11:26:55 -0400	[thread overview]
Message-ID: <20170510152655.GD19962@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170509134623.13120-1-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

On Tue, May 09, 2017 at 02:46:19PM +0100, Daniel P. Berrange wrote:
> The following changes since commit dd1559bb267becbb838de41132ef60771d183e5d:
> 
>   Merge remote-tracking branch 'elmarco/tags/chr-tests-pull-request' into staging (2017-05-05 17:07:55 +0100)
> 
> are available in the git repository at:
> 
>   git://github.com/berrange/qemu tags/pull-qcrypto-2017-05-09-1
> 
> for you to fetch changes up to a37278169d0d7d33270c6817f4a2e4f7345e1098:
> 
>   crypto: qcrypto_random_bytes() now works on windows w/o any other crypto libs (2017-05-09 14:41:47 +0100)
> 
> ----------------------------------------------------------------
> Merge qcrypto 2017/05/09 v1
> 
> ----------------------------------------------------------------
> 
> Daniel P. Berrange (3):
>   Default to GSSAPI (Kerberos) instead of DIGEST-MD5 for SASL
>   List SASL config file under the cryptography maintainer's realm
>   crypto: move 'opaque' parameter to (nearly) the end of parameter list
> 
> Geert Martin Ijewski (1):
>   crypto: qcrypto_random_bytes() now works on windows w/o any other
>     crypto libs
> 
>  MAINTAINERS               |  1 +
>  block/crypto.c            |  6 +++---
>  crypto/block-luks.c       | 13 +++++++-----
>  crypto/init.c             |  6 ++++++
>  crypto/random-gcrypt.c    |  2 ++
>  crypto/random-gnutls.c    |  3 +++
>  crypto/random-platform.c  | 45 ++++++++++++++++++++++++++++++++-------
>  include/crypto/block.h    |  6 +++---
>  include/crypto/random.h   |  9 ++++++++
>  qemu-doc.texi             | 50 +++++++++++++++++++++++++------------------
>  qemu.sasl                 | 54 +++++++++++++++++++++++++++--------------------
>  tests/test-crypto-block.c |  6 +++---
>  12 files changed, 135 insertions(+), 66 deletions(-)
> 
> -- 
> 2.9.3
> 
> 

Thanks, applied to my staging tree:
https://github.com/stefanha/qemu/commits/staging

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      parent reply	other threads:[~2017-05-10 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 13:46 [Qemu-devel] [PULL v1 0/4] Merge qcrypto 2017/05/07 Daniel P. Berrange
2017-05-09 13:46 ` [Qemu-devel] [PULL v1 1/4] Default to GSSAPI (Kerberos) instead of DIGEST-MD5 for SASL Daniel P. Berrange
2017-05-09 13:46 ` [Qemu-devel] [PULL v1 2/4] List SASL config file under the cryptography maintainer's realm Daniel P. Berrange
2017-05-09 13:46 ` [Qemu-devel] [PULL v1 3/4] crypto: move 'opaque' parameter to (nearly) the end of parameter list Daniel P. Berrange
2017-05-09 13:46 ` [Qemu-devel] [PULL v1 4/4] crypto: qcrypto_random_bytes() now works on windows w/o any other crypto libs Daniel P. Berrange
2017-05-10 15:26 ` Stefan Hajnoczi [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=20170510152655.GD19962@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).