qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: drop trailing empty strings
Date: Mon, 8 Feb 2016 15:11:47 +0000	[thread overview]
Message-ID: <20160208151147.GC31586@stefanha-x1.localdomain> (raw)
In-Reply-To: <20160118192843.55ef9d93@bahia.huguette.org>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Mon, Jan 18, 2016 at 07:28:43PM +0100, Greg Kurz wrote:
> On Mon, 18 Jan 2016 20:37:58 +0300
> Michael Tokarev <mjt@tls.msk.ru> wrote:
> 
> > 11.01.2016 20:30, Greg Kurz wrote:
> > 
> > > -virtio_balloon_handle_output(const char *name, uint64_t gpa) "section name: %s gpa: %"PRIx64""
> > > +virtio_balloon_handle_output(const char *name, uint64_t gpa) "section name: %s gpa: %"PRIx64  
> > ...
> > 
> > I'm not sure what's the value of this.  It's fine either way, no?
> 
> The only value is to drop unneeded stuff... and maybe some consistency
> with the traces that don't have these trailing empty strings.
> 
> > Do we have a rule for trailing empty strings in coding style? :)
> > 
> 
> Nor we have against parenthesitis, which brings a lot more unneeded
> characters into the code :P

Regarding the history of the quoting limitation, see commit
cf85cf8e972f3ad79f203be4edb7968d6e052293 ("trace: Format strings must
begin/end with double quotes").  It was a limitation of the old
tracetool.sh script.

The modern tracetool.py script handles format strings fine when they do
not end with double-quotes.

Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-02-08 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 17:30 [Qemu-devel] [PATCH] trace: drop trailing empty strings Greg Kurz
2016-01-15 17:24 ` Eric Blake
2016-01-18 17:37 ` Michael Tokarev
2016-01-18 18:28   ` Greg Kurz
2016-02-08 15:11     ` Stefan Hajnoczi [this message]
2016-02-08 15:39       ` Markus Armbruster
2016-02-09 16:05         ` Stefan Hajnoczi
2016-01-19  7:35 ` Markus Armbruster

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=20160208151147.GC31586@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).