qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/1] chardev: support for authorization control on TLS connections
Date: Thu, 7 Mar 2019 12:21:43 +0000	[thread overview]
Message-ID: <20190307122143.GU32268@redhat.com> (raw)
In-Reply-To: <20190227135523.16952-1-berrange@redhat.com>

ping - soft freeze is less than a week away & I would like to see this
in a chardev pull request in time for 4.0

On Wed, Feb 27, 2019 at 01:55:22PM +0000, Daniel P. Berrangé wrote:
> This series provides the chardev part of the authorization control series
> previously posted as:
> 
>   v1: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg04482.html
>   v2: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg05727.html
>   v3: https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg01639.html
>   v4: https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg04319.html
> 
> The core authz framework is now merged & this patch has previously
> had positive review, but I removed the r-b due to need for changes
> to resolve merge conflicts with current chardev code. I expect this
> is none the less ready for the chardev tree, should the maintainer
> consider it acceptable.
> 
> Daniel P. Berrangé (1):
>   chardev: add support for authorization for TLS clients
> 
>  chardev/char-socket.c | 12 +++++++++++-
>  chardev/char.c        |  3 +++
>  qapi/char.json        |  6 ++++++
>  qemu-options.hx       |  9 +++++++--
>  4 files changed, 27 insertions(+), 3 deletions(-)
> 
> -- 
> 2.20.1
> 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      parent reply	other threads:[~2019-03-07 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 13:55 [Qemu-devel] [PATCH 0/1] chardev: support for authorization control on TLS connections Daniel P. Berrangé
2019-02-27 13:55 ` [Qemu-devel] [PATCH 1/1] chardev: add support for authorization for TLS clients Daniel P. Berrangé
2019-02-27 14:29   ` Philippe Mathieu-Daudé
2019-03-07 18:51   ` Marc-André Lureau
2019-03-07 19:00     ` Eric Blake
2019-03-07 12:21 ` Daniel P. Berrangé [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=20190307122143.GU32268@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@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 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).