All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>, Le Tan <tamlokveer@gmail.com>,
	 qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-trivial@nongnu.org,
	peter.crosthwaite@xilinx.com, afaerber@suse.de,
	stefanha@redhat.com
Subject: Re: [Qemu-trivial] [PATCH v3] block: replace fprintf(stderr, ...) with error_report()
Date: Sun, 25 May 2014 18:36:04 +0400	[thread overview]
Message-ID: <5381FFD4.8080107@msgid.tls.msk.ru> (raw)
In-Reply-To: <5381FE37.80904@web.de>

25.05.2014 18:29, Jan Kiszka wrote:
> On 2014-05-25 10:44, Le Tan wrote:
>> Replace fprintf(stderr,...) with error_report() in files block/*, block.c,
>> block-migration.c and blockdev.c. The trailing "\n"s of the @fmt argument
>> have been removed because @fmt of error_report() should not contain newline.
>> Also fix some coding style issues.
> 
> Let's do the "also" part in a separate patch. It's more than one or two
> trivial pass-by style fixes, and some people may like the fprintf
> conversion while having different views on the other changes.

I think he misunderstood.

I told him that his previous patch had its own whitespace issues,
ie, it _adds_ whitespace errors.

In another reply I told him it is usually a good idea to fix style
issues in the code the patch touches -- this means, close to, if a
line being changed for something else has an unrelated style issue,
it should be fixed too.  (An example was space between function name
and its arguments in fprintf argument list, while converting that
fprintf to error_report).

But it looks like he took this advise in much more broad way and
fixed _all_ whitespace/style issues in the files he touches.  Oh
well.. :)

And yes, definitely, please don't mix it like this.  Usually, these
code style issues should not be touched by its own, only if you
change nearby code.

Thanks,

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>, Le Tan <tamlokveer@gmail.com>,
	qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-trivial@nongnu.org,
	peter.crosthwaite@xilinx.com, afaerber@suse.de,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v3] block: replace fprintf(stderr, ...) with error_report()
Date: Sun, 25 May 2014 18:36:04 +0400	[thread overview]
Message-ID: <5381FFD4.8080107@msgid.tls.msk.ru> (raw)
In-Reply-To: <5381FE37.80904@web.de>

25.05.2014 18:29, Jan Kiszka wrote:
> On 2014-05-25 10:44, Le Tan wrote:
>> Replace fprintf(stderr,...) with error_report() in files block/*, block.c,
>> block-migration.c and blockdev.c. The trailing "\n"s of the @fmt argument
>> have been removed because @fmt of error_report() should not contain newline.
>> Also fix some coding style issues.
> 
> Let's do the "also" part in a separate patch. It's more than one or two
> trivial pass-by style fixes, and some people may like the fprintf
> conversion while having different views on the other changes.

I think he misunderstood.

I told him that his previous patch had its own whitespace issues,
ie, it _adds_ whitespace errors.

In another reply I told him it is usually a good idea to fix style
issues in the code the patch touches -- this means, close to, if a
line being changed for something else has an unrelated style issue,
it should be fixed too.  (An example was space between function name
and its arguments in fprintf argument list, while converting that
fprintf to error_report).

But it looks like he took this advise in much more broad way and
fixed _all_ whitespace/style issues in the files he touches.  Oh
well.. :)

And yes, definitely, please don't mix it like this.  Usually, these
code style issues should not be touched by its own, only if you
change nearby code.

Thanks,

/mjt

  reply	other threads:[~2014-05-25 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  2:44 [Qemu-trivial] [PATCH v3] block: replace fprintf(stderr, ...) with error_report() Le Tan
2014-05-25  2:44 ` [Qemu-devel] " Le Tan
2014-05-25 14:29 ` [Qemu-trivial] " Jan Kiszka
2014-05-25 14:29   ` [Qemu-devel] " Jan Kiszka
2014-05-25 14:36   ` Michael Tokarev [this message]
2014-05-25 14:36     ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-05-25 14:45     ` Le Tan
2014-05-25 14:45       ` [Qemu-devel] " Le Tan
2014-05-25 14:48       ` Michael Tokarev
2014-05-25 14:48         ` [Qemu-devel] " Michael Tokarev

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=5381FFD4.8080107@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=afaerber@suse.de \
    --cc=jan.kiszka@web.de \
    --cc=kwolf@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=tamlokveer@gmail.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 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.