qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, cohuck@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] trace-events: print 0x before hex numbers
Date: Tue, 1 Aug 2017 10:47:26 +0100	[thread overview]
Message-ID: <20170801094726.GD13521@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170731160135.12101-1-vsementsov@virtuozzo.com>

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

On Mon, Jul 31, 2017 at 07:01:31PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
> 
> It is hard to read logs, when there are hex and dec numbers in one line, when
> hex number doesn't contain any letters and don't have '0x' prefix.
> 
> So, here is a complete solution for the problem:
> 
> - add information into CODING_STYLE
> - add a check into checkpatch.pl
> - fix current state
> 
> The new rule for the style is:
> 
> Hex numbers should be prefixed by '0x', except groups of numbers,
> separated by symbols ' ', '.', ':', '/', however '0x' can be used for
> numbers in such groups too. Flag '#' in number format is not allowed.
> 
> Note: checkpatch fails on checkpatch change (03) due to long lines.
> It is because checkpatch.pl is indented by tabs and when it checks
> for long lines it consider tabs as 8 spaces. Looks like nobody cares,
> so do I. I see two ways here:
>  -  s/\t/    /g
>  -  make exclusion in checkpatch.pl for checkpatch.pl to consider tabs
>     as 4 spaces, not 8.  However I don't want to fix it in the context
>     of these series.
> 
> v3: 01 - rewording
>     02 - adjust commit message - add two printf flags "'I" into a check
>          add Stefan's and Eric's r-bs
>     03 - fix commit message s/Accordingly/According/
>          add Stefan's r-b
>     04 - add Stefan's r-b
>          add Cornelia's a-b
> v2: almost everything (style, checkpatch, excluding number groups)
> V1: was a draft of the idea using two sed commands.
> 
> Vladimir Sementsov-Ogievskiy (4):
>   coding_style: add point about 0x in trace-events
>   trace-events: fix code style: %# -> 0x%
>   checkpatch: check trace-events code style
>   trace-events: fix code style: print 0x before hex numbers
> 
>  CODING_STYLE              |  35 +++++++++
>  accel/tcg/trace-events    |   2 +-
>  audio/trace-events        |   4 +-
>  block/trace-events        |  28 ++++----
>  hw/audio/trace-events     |   4 +-
>  hw/char/trace-events      |  12 ++--
>  hw/display/trace-events   |  14 ++--
>  hw/dma/trace-events       |  20 +++---
>  hw/i386/xen/trace-events  |  26 +++----
>  hw/input/trace-events     |   6 +-
>  hw/intc/trace-events      | 176 +++++++++++++++++++++++-----------------------
>  hw/isa/trace-events       |   4 +-
>  hw/misc/trace-events      |  78 ++++++++++----------
>  hw/net/trace-events       |  52 +++++++-------
>  hw/nvram/trace-events     |   2 +-
>  hw/pci/trace-events       |   4 +-
>  hw/ppc/trace-events       |  64 ++++++++---------
>  hw/s390x/trace-events     |  20 +++---
>  hw/scsi/trace-events      | 118 +++++++++++++++----------------
>  hw/sd/trace-events        |   4 +-
>  hw/timer/trace-events     |  20 +++---
>  hw/usb/trace-events       |  56 +++++++--------
>  hw/vfio/trace-events      |  44 ++++++------
>  hw/virtio/trace-events    |   6 +-
>  hw/xen/trace-events       |   8 +--
>  linux-user/trace-events   |  10 +--
>  migration/trace-events    |  36 +++++-----
>  nbd/trace-events          |  18 ++---
>  net/trace-events          |   4 +-
>  scripts/checkpatch.pl     |  19 +++++
>  target/arm/trace-events   |  10 +--
>  target/s390x/trace-events |   2 +-
>  target/sparc/trace-events |  30 ++++----
>  trace-events              |  20 +++---
>  34 files changed, 505 insertions(+), 451 deletions(-)
> 
> -- 
> 2.11.1
> 

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

Stefan

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

      parent reply	other threads:[~2017-08-01  9:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 16:01 [Qemu-devel] [PATCH v3 0/4] trace-events: print 0x before hex numbers Vladimir Sementsov-Ogievskiy
2017-07-31 16:01 ` [Qemu-devel] [PATCH v3 1/4] coding_style: add point about 0x in trace-events Vladimir Sementsov-Ogievskiy
2017-07-31 16:07   ` Eric Blake
2017-07-31 16:01 ` [Qemu-devel] [PATCH v3 2/4] trace-events: fix code style: %# -> 0x% Vladimir Sementsov-Ogievskiy
2017-07-31 16:15   ` Eric Blake
2017-07-31 16:40     ` Vladimir Sementsov-Ogievskiy
2017-07-31 16:01 ` [Qemu-devel] [PATCH v3 3/4] checkpatch: check trace-events code style Vladimir Sementsov-Ogievskiy
2017-07-31 16:01 ` [Qemu-devel] [PATCH v3 4/4] trace-events: fix code style: print 0x before hex numbers Vladimir Sementsov-Ogievskiy
2017-07-31 16:25 ` [Qemu-devel] [PATCH v3 0/4] trace-events: " no-reply
2017-08-01  9:47 ` Stefan Hajnoczi [this message]

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=20170801094726.GD13521@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@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).