From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, eblake@redhat.com,
mreitz@redhat.com, jsnow@redhat.com, den@openvz.org,
peter.maydell@linaro.org, berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/4] trace-events: fix code style: %# -> 0x%
Date: Mon, 31 Jul 2017 10:24:32 +0100 [thread overview]
Message-ID: <20170731092432.GC11830@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170729131159.24949-3-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On Sat, Jul 29, 2017 at 04:11:57PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> In trace format '#' flag of printf is forbidden. Fix it to '0x%'.
>
> This patch is created by the following:
>
> check that we have a problem
> > find . -name trace-events | xargs grep '%#' | wc -l
> 56
>
> check that there are no cases with additional printf flags
> > find . -name trace-events | xargs grep '%[-+ 0]+#' | wc -l
> 0
>
> check that there are no wrong usage of '#' and '0x' together
> > find . -name trace-events | xargs grep '0x%#' | wc -l
> 0
>
> fix the problem
> > find . -name trace-events | xargs sed -i 's/%#/0x%/g'
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> audio/trace-events | 4 ++--
> block/trace-events | 6 +++---
> hw/display/trace-events | 2 +-
> hw/i386/xen/trace-events | 22 +++++++++++-----------
> hw/input/trace-events | 2 +-
> hw/intc/trace-events | 20 ++++++++++----------
> hw/net/trace-events | 18 +++++++++---------
> hw/pci/trace-events | 4 ++--
> hw/scsi/trace-events | 6 +++---
> hw/xen/trace-events | 8 ++++----
> trace-events | 20 ++++++++++----------
> 11 files changed, 56 insertions(+), 56 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-07-31 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 13:11 [Qemu-devel] [PATCH v2 0/4] trace-events: print 0x before hex numbers Vladimir Sementsov-Ogievskiy
2017-07-29 13:11 ` [Qemu-devel] [PATCH v2 1/4] coding_style: add point about 0x in trace-events Vladimir Sementsov-Ogievskiy
2017-07-31 9:19 ` Stefan Hajnoczi
2017-07-31 12:45 ` Eric Blake
2017-07-29 13:11 ` [Qemu-devel] [PATCH v2 2/4] trace-events: fix code style: %# -> 0x% Vladimir Sementsov-Ogievskiy
2017-07-31 9:24 ` Stefan Hajnoczi [this message]
2017-07-31 12:48 ` Eric Blake
2017-07-29 13:11 ` [Qemu-devel] [PATCH v2 3/4] checkpatch: check trace-events code style Vladimir Sementsov-Ogievskiy
2017-07-31 9:26 ` Stefan Hajnoczi
2017-07-31 12:48 ` Eric Blake
2017-07-29 13:11 ` [Qemu-devel] [PATCH v2 4/4] trace-events: fix code style: print 0x before hex numbers Vladimir Sementsov-Ogievskiy
2017-07-31 9:36 ` Stefan Hajnoczi
2017-07-31 9:49 ` Cornelia Huck
2017-07-31 15:05 ` Vladimir Sementsov-Ogievskiy
2017-07-31 15:38 ` Cornelia Huck
2017-07-29 13:32 ` [Qemu-devel] [PATCH v2 0/4] trace-events: " no-reply
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=20170731092432.GC11830@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).