All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL for-2.12 0/3] Qcrypto next patches
Date: Fri,  6 Apr 2018 14:30:43 +0100	[thread overview]
Message-ID: <20180406133046.5682-1-berrange@redhat.com> (raw)

The following changes since commit 0e87fdc966d05f4e5ad868034fcd8ee2a08ca62d:

  Update version for v2.12.0-rc2 release (2018-04-04 20:37:20 +0100)

are available in the Git repository at:

  https://github.com/berrange/qemu tags/qcrypto-next-pull-request

for you to fetch changes up to 057ad0b46992e3ec4ce29b9103162aa3c683f347:

  crypto: ensure we use a predictable TLS priority setting (2018-04-06 11:28:31 +0100)

----------------------------------------------------------------

Two improvements to TLS docs, and a fix for the test suite to
avoid breakage on Fedora >= 28

----------------------------------------------------------------

Christophe Fergeau (1):
  docs: Document -object tls-creds-x509 priority=xxx

Daniel P. Berrangé (2):
  docs: update information for TLS certificate management
  crypto: ensure we use a predictable TLS priority setting

 qemu-doc.texi                  | 364 ++++++++++++++++++++++++++++++-----------
 qemu-options.hx                |  11 +-
 tests/test-crypto-tlssession.c |   1 +
 tests/test-io-channel-tls.c    |   1 +
 4 files changed, 284 insertions(+), 93 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-04-06 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 13:30 Daniel P. Berrangé [this message]
2018-04-06 13:30 ` [Qemu-devel] [PULL 1/3] docs: update information for TLS certificate management Daniel P. Berrangé
2018-04-06 13:30 ` [Qemu-devel] [PULL 2/3] docs: Document -object tls-creds-x509 priority=xxx Daniel P. Berrangé
2018-04-06 13:30 ` [Qemu-devel] [PULL 3/3] crypto: ensure we use a predictable TLS priority setting Daniel P. Berrangé
2018-04-06 18:13 ` [Qemu-devel] [PULL for-2.12 0/3] Qcrypto next patches 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=20180406133046.5682-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --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.