qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Markus Armbruster <armbru@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Andreas Faerber <afaerber@suse.de>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] CODING_STYLE, checkpatch: update line length rules
Date: Wed, 9 Sep 2015 22:28:32 +0200	[thread overview]
Message-ID: <55F09670.9040405@redhat.com> (raw)
In-Reply-To: <CAFEAcA_FPDkOOjo29ePemhqQfgbbt22_4gyu+tmhLz=ScA9_1w@mail.gmail.com>



On 09/09/2015 19:22, Peter Maydell wrote:
> On 7 September 2015 at 18:05, Markus Armbruster <armbru@redhat.com> wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>> That said, and even though Thomas obviously hasn't read the previous
>>> discussion, :) I do believe that 76 characters is too strict a limit.
>>
>> It's not a strict limit, it's a warning.  The strict limit is 90.
> 
> I tend to bounce patches on review for checkpatch warnings...
> I don't make much distinction between a warning and an error.

Doing something about this is the point of this series.  As a start, it
enables a few more warnings (patch 3) so that maintainers start seeing
them and get used to them.  Some may reject patches altogether based on
the warnings, some may not.

With just a few exceptions (tabs, line lengths, braces) it makes a lot
of sense to fix warnings in the whole tree with a single sweeping
change.  If we agree about this, we can upgrade warnings to error at the
time of the fix, or even before.

Ultimately, warnings should be used only for things that are _really_
subjective, so that we can aim at an error-free (but not warning-free)
"checkpatch -f".

Paolo

  parent reply	other threads:[~2015-09-09 20:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07  9:53 [Qemu-devel] [PATCH 0/4] updates to coding style and checkpatch Paolo Bonzini
2015-09-07  9:53 ` [Qemu-devel] [PATCH 1/4] CODING_STYLE: update mixed declaration rules Paolo Bonzini
2015-09-09  9:20   ` Stefan Hajnoczi
2015-09-09 10:43   ` Alex Bennée
2015-09-07  9:53 ` [Qemu-devel] [PATCH 2/4] CODING_STYLE, checkpatch: update line length rules Paolo Bonzini
2015-09-07 13:18   ` Thomas Huth
2015-09-07 14:22     ` Paolo Bonzini
2015-09-07 14:37       ` Thomas Huth
2015-09-07 15:23         ` Markus Armbruster
2015-09-07 16:06           ` Paolo Bonzini
2015-09-07 17:05             ` Markus Armbruster
2015-09-09 16:26               ` John Snow
2015-09-09 17:22               ` Peter Maydell
2015-09-09 19:23                 ` Eduardo Habkost
2015-09-09 20:28                 ` Paolo Bonzini [this message]
2015-09-09 19:09             ` Eduardo Habkost
2015-09-07 17:02           ` Thomas Huth
2015-09-09 18:45             ` Eduardo Habkost
2015-09-07 15:17   ` Markus Armbruster
2015-09-07 15:54     ` Paolo Bonzini
2015-09-07 16:59       ` Markus Armbruster
2015-09-07  9:53 ` [Qemu-devel] [PATCH 3/4] checkpatch: adapt some tests to QEMU Paolo Bonzini
2015-09-09  9:22   ` Stefan Hajnoczi
2015-09-17 14:24   ` Peter Maydell
2015-09-17 16:00     ` Paolo Bonzini
2015-09-17 16:16       ` Peter Maydell
2015-09-17 16:32         ` Paolo Bonzini
2015-09-17 16:44           ` Eric Blake
2015-09-18  6:53             ` Markus Armbruster
2015-10-04 18:44           ` Peter Maydell
2015-10-05 18:11             ` Eduardo Habkost
2015-10-05 18:47               ` Peter Maydell
2015-10-05 19:27                 ` Paolo Bonzini
2015-09-07  9:53 ` [Qemu-devel] [PATCH 4/4] checkpatch: remove tests that are not relevant outside the kernel Paolo Bonzini

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=55F09670.9040405@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).