qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Fritsch <sf@sfritsch.de>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
	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: Fri, 30 Jun 2017 17:53:32 +0200	[thread overview]
Message-ID: <2070055.lQvcDpnNFn@k> (raw)
In-Reply-To: <20170629150054.GB22733@work-vm>

On Thursday, 29 June 2017 16:00:54 CEST Dr. David Alan Gilbert wrote:
> * 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'.

I also think that "send a break" is best for people who google for it.

Thanks.

Cheers,
Stefan

  reply	other threads:[~2017-06-30 15:53 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
2017-06-30 15:53     ` Stefan Fritsch [this message]
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=2070055.lQvcDpnNFn@k \
    --to=sf@sfritsch.de \
    --cc=armbru@redhat.com \
    --cc=dgilbert@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).