qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH 00/11] trivial: Remove superfluous '\n' around error_report/error_setg
Date: Thu, 12 Feb 2015 09:10:54 +0800	[thread overview]
Message-ID: <54DBFD9E.8060808@huawei.com> (raw)
In-Reply-To: <87vbj87ehb.fsf@blackfin.pond.sub.org>

On 2015/2/11 21:41, Markus Armbruster wrote:
> <arei.gonglei@huawei.com> writes:
> 
>> From: Gonglei <arei.gonglei@huawei.com>
>>
>> Yesterday, I found that some files have superfluous '\n' character
>> around error_report/error_setg when reviewed patches.
>>
>> By a simply script, the below files were listed. Classify and fix
>> them. It's suitable for applying via qemu-trivial IMHO.
> 
> You can find my script in commit 312fd5f :)
> 
It's cool, I haven't noticed it before.  :)
>> Gonglei (11):
>>   block: remove superfluous '\n' around error_report/error_setg
>>   a9gtimer: remove superfluous '\n' around error_setg
>>   pl330.c: remove superfluous '\n' around error_setg
>>   numa: remove superfluous '\n' around error_setg
>>   Remove superfluous '\n' around error_report()
>>   vhost-scsi: Remove superfluous '\n' around error_report()
>>   vfio: Remove superfluous '\n' around error_report()
>>   xtensa: Remove superfluous '\n' around error_report()
>>   tpm: Remove superfluous '\n' around error_report()
>>   arm/digic_boards: Remove superfluous '\n' around error_report()
>>   vhost: Remove superfluous '\n' around error_report()
> 
> When I fixed this before, I didn't split it up (commits 312fd5f 6daf194
> be62a2eb).  Splitting it up is fine, of course.  Having the catch-all as
> PATCH 05/11 is a bit odd, though.  Its qemu-img.c hunk could go into
> PATCH 01, because qemu-img is part of the block subsystem.  Not worth a
> respin as far as I'm concerned.
> 
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> 
Thanks.

Regards,
-Gonglei

      reply	other threads:[~2015-02-12  1:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  4:12 [Qemu-devel] [PATCH 00/11] trivial: Remove superfluous '\n' around error_report/error_setg arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 01/11] block: remove " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 02/11] a9gtimer: remove superfluous '\n' around error_setg arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 03/11] pl330.c: " arei.gonglei
2015-02-16  9:45   ` Michael Tokarev
2015-02-25  4:18     ` Gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 04/11] numa: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 05/11] Remove superfluous '\n' around error_report() arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 06/11] vhost-scsi: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 07/11] vfio: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 08/11] xtensa: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 09/11] tpm: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 10/11] arm/digic_boards: " arei.gonglei
2015-02-11  4:12 ` [Qemu-devel] [PATCH 11/11] vhost: " arei.gonglei
2015-02-11 13:41 ` [Qemu-devel] [PATCH 00/11] trivial: Remove superfluous '\n' around error_report/error_setg Markus Armbruster
2015-02-12  1:10   ` Gonglei [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=54DBFD9E.8060808@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --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).