All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Stefan Fritsch" <sf@sfritsch.de>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
Date: Thu, 29 Jun 2017 16:00:54 +0100	[thread overview]
Message-ID: <20170629150054.GB22733@work-vm> (raw)
In-Reply-To: <d95a3198-3ad0-4a75-dda2-a3b7502ede28@redhat.com>

* Eric Blake (eblake@redhat.com) wrote:
> On 06/11/2017 02:48 AM, Stefan Fritsch wrote:
> > Sending a break on a serial console can be useful for debugging the
> > guest. But not all chardev backends support sending breaks (only telnet
> > and mux do). The chardev-send-break command allows to send a break even
> > if using other backends.
> > 
> > Signed-off-by: Stefan Fritsch <sf@sfritsch.de>
> > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> > v2: added tests and Acked-by line
> > 
> 
> > +++ b/hmp-commands.hx
> > @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
> >  ETEXI
> >  
> >      {
> > +        .name       = "chardev-send-break",
> > +        .args_type  = "id:s",
> > +        .params     = "id",
> > +        .help       = "send break on chardev",
> 
> Compare this wording,...
> 
> > +STEXI
> > +@item chardev-send-break id
> > +@findex chardev-send-break
> > +Sends break on the chardev @var{id}.
> 
> repeated here,
> 
> > +++ b/qapi-schema.json
> > @@ -5114,6 +5114,26 @@
> >  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
> >  
> >  ##
> > +# @chardev-send-break:
> > +#
> > +# Send a break to a character device
> 
> ...with this wording.  I like 'send a break' better than 'send break',
> but even better might be 'send a break sequence' or even 'emulate a
> break sequence' (by definition, a break is NOT a character, but on bare
> metal character devices it IS a defined electrical sequence distinct
> from characters to make the recipient aware that the sender is trying to
> get attention).
> 
> Otherwise, the patch looks fine to me.  If all that changes is some
> word-smithing (and the maintainer may be willing to do that), you can add:
> Reviewed-by: Eric Blake <eblake@redhat.com>

I'll go with the 'send a break' - the official terminology seems to
be a 'break condition', but I've never heard anyone say that,
it's always been 'send a break'.

diff --git a/hmp-commands.hx b/hmp-commands.hx
index fc8d54b52a..275ccdfbc7 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -1748,7 +1748,7 @@ ETEXI
         .name       = "chardev-send-break",
         .args_type  = "id:s",
         .params     = "id",
-        .help       = "send break on chardev",
+        .help       = "send a break on chardev",
         .cmd        = hmp_chardev_send_break,
         .command_completion = chardev_remove_completion,
     },
@@ -1756,7 +1756,7 @@ ETEXI
 STEXI
 @item chardev-send-break id
 @findex chardev-send-break
-Sends break on the chardev @var{id}.
+Send a break on the chardev @var{id}.

 ETEXI


Queued to HMP

Dave

> 
> -- 
> Eric Blake, Principal Software Engineer
> Red Hat, Inc.           +1-919-301-3266
> Virtualization:  qemu.org | libvirt.org
> 



--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2017-06-29 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11  7:48 [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command Stefan Fritsch
2017-06-27 19:40 ` Eric Blake
2017-06-29 14:27   ` Marc-André Lureau
2017-06-29 14:41     ` Dr. David Alan Gilbert
2017-06-29 15:00   ` Dr. David Alan Gilbert [this message]
2017-06-30 15:53     ` Stefan Fritsch
2017-07-19 15:01 ` Thomas Huth
2017-07-19 15:14   ` Stefan Fritsch

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=20170629150054.GB22733@work-vm \
    --to=dgilbert@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sf@sfritsch.de \
    /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.