qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qapi: convert add_client
Date: Tue, 18 Sep 2012 16:20:34 -0300	[thread overview]
Message-ID: <20120918162034.4e416a1c@doriath.home> (raw)
In-Reply-To: <5058C7CC.1030004@redhat.com>

On Tue, 18 Sep 2012 13:13:16 -0600
Eric Blake <eblake@redhat.com> wrote:

> On 09/18/2012 01:06 PM, Luiz Capitulino wrote:
> > Also fixes a few issues while there:
> > 
> >  1. The fd returned by monitor_get_fd() leaks in most error conditions
> >  2. monitor_get_fd() return value is not checked. Best case we get
> >     an error that is not correctly reported, worse case one of the
> >     functions using the fd (with value of -1) will explode
> >  3. A few error conditions aren't reported
> > 
> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > ---
> >  monitor.c        | 39 ---------------------------------------
> >  qapi-schema.json | 23 +++++++++++++++++++++++
> >  qmp-commands.hx  |  5 +----
> >  qmp.c            | 44 ++++++++++++++++++++++++++++++++++++++++++++
> >  4 files changed, 68 insertions(+), 43 deletions(-)
> > 
> 
> >  { 'command': 'screendump', 'data': {'filename': 'str'} }
> > +
> > +##
> > +# @add_client
> 
> Are these supposed to be sorted in any particular order?

Honestly, this is something I've paid very little attention to. But it's
a good idea to keep the list sorted yes (although I'd like ErroClass to
be the first item).

> 
> > +#
> > +# Allow client connections for VNC, Spice and socket based
> > +# character devices to be passed in to QEMU via SCM_RIGHTS.
> > +#
> > +# @protocol: protocol name. Valid names are "vnc", "spice" or the
> > +#            name of a character device (eg. from -chardev id=XXXX)
> > +#
> > +# @fdname: file descriptor name passed via SCM_RIGHTS
> 
> Misleading; isn't this really:
> 
> file descriptor name previously passed via 'getfd' command
> 
> since it is only 'getfd' that uses SCM_RIGHTS?

You're right, of course. Stupid mistake from my part :)

> > +#
> > +# skipauth: #optional whether to skip authentication
> > +#
> > +# tls: #optional whether to perform TLS
> 
> Missing leading @ on two lines.

Will fix.

> > +#
> > +# Returns: nothing on success.
> > +#
> > +# Since: 0.14.0
> 
> If this were a new command for 1.3, I'd say to name it 'add-client'; but
> since QMP has already been exposing it and you are now just documenting
> it, you can't change the name.

Yes, we just have to live with that for all old commands.

  reply	other threads:[~2012-09-18 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 19:06 [Qemu-devel] [PATCH] qapi: convert add_client Luiz Capitulino
2012-09-18 19:13 ` Eric Blake
2012-09-18 19:20   ` Luiz Capitulino [this message]
2012-09-19  7:08     ` Markus Armbruster
2012-09-19 13:52       ` Luiz Capitulino
2012-09-19 11:04 ` Paolo Bonzini
2012-09-19 13:57   ` Luiz Capitulino

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=20120918162034.4e416a1c@doriath.home \
    --to=lcapitulino@redhat.com \
    --cc=eblake@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).