From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
John Ferlan <jferlan@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.9 v3 0/2] migration: fixes to handling tls-hostname/tls-creds
Date: Thu, 2 Mar 2017 13:08:25 -0600 [thread overview]
Message-ID: <6e8da3a1-9533-cd39-34e9-e4fd27f53f15@redhat.com> (raw)
In-Reply-To: <20170302161921.10181-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On 03/02/2017 10:19 AM, Daniel P. Berrange wrote:
> The need for these two patches was identified during implementation of
> TLS encrypted migration in libvirt.
>
> Changed in v3:
>
> - Add to qapi-schema.json docs
>
> Daniel P. Berrange (2):
> migration: allow clearing migration string parameters
> migration: always report tls-creds & tls-hostname migrate parameters
>
> migration/migration.c | 22 ++++++++++++++++------
> qapi-schema.json | 8 +++++++-
> 2 files changed, 23 insertions(+), 7 deletions(-)
The discoverability of whether "" works is not visible in introspection,
but reporting "" on output helps. For the series:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-03-02 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 16:19 [Qemu-devel] [PATCH v3 0/2] migration: fixes to handling tls-hostname/tls-creds Daniel P. Berrange
2017-03-02 16:19 ` [Qemu-devel] [PATCH v3 1/2] migration: allow clearing migration string parameters Daniel P. Berrange
2017-03-02 16:19 ` [Qemu-devel] [PATCH v3 2/2] migration: always report tls-creds & tls-hostname migrate parameters Daniel P. Berrange
2017-03-02 19:08 ` Eric Blake [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=6e8da3a1-9533-cd39-34e9-e4fd27f53f15@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jdenemar@redhat.com \
--cc=jferlan@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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.