From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] checkpatch.pl: warn on C99 comments, but don't fail
Date: Fri, 01 Apr 2011 11:55:39 -0500 [thread overview]
Message-ID: <4D96038B.3020703@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTi=_MKeak8yy+GFLjdLd4mV9vbkDKQ2BEA-GEBr1@mail.gmail.com>
On 04/01/2011 11:16 AM, Peter Maydell wrote:
> On 1 April 2011 16:59, Stefan Hajnoczi<stefanha@gmail.com> wrote:
>> On Fri, Apr 1, 2011 at 4:52 PM, Peter Maydell<peter.maydell@linaro.org> wrote:
>>> On 1 April 2011 16:20, Michael Roth<mdroth@linux.vnet.ibm.com> wrote:
>>>> We also make C99 //comments a warning instead of an error, since they
>>>> don't actually violate QEMU's coding guidelines.
>>>
>>> We should either update the guidelines or fix the script...
>>
>> There are a whole bunch of // in the codebase. I prefer /* */ but as
>> it stands I think // should not even raise a warning.
>
> I don't care much either, really. I just don't think we should be
> introducing random coding standards rules by the back door because
> checkpatch happens to complain about them.
Whether or not // comments should also be a warning...I'm not sure. It
seems like a reasonable "suggestion" to make though, since mixed comment
styles makes code look nastier. I could also go either way though...
But there *are* some warnings that make sense to complain about without
saying "you can't do this", like extern's in .c files: some cases are
exceptional.
I'd prefer to only document "strict" guidelines, and treat checkpatch.pl
warnings ("suggestions") as an extra "reward" you get for taking the
time to run it.
>
> -- PMM
next prev parent reply other threads:[~2011-04-01 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 15:20 [Qemu-devel] checkpatch.pl: warn on C99 comments, but don't fail Michael Roth
2011-04-01 15:20 ` [Qemu-devel] [PATCH 1/2] checkpatch.pl: add --no-fail-on-warn option Michael Roth
2011-04-01 15:20 ` [Qemu-devel] [PATCH 2/2] checkpatch.pl: make C99 comments a warning, not error Michael Roth
2011-04-01 15:33 ` [Qemu-devel] " Michael Roth
2011-04-01 15:49 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-01 18:46 ` Blue Swirl
2011-04-02 14:02 ` Stefan Hajnoczi
2011-04-01 15:52 ` [Qemu-devel] checkpatch.pl: warn on C99 comments, but don't fail Peter Maydell
2011-04-01 15:59 ` Stefan Hajnoczi
2011-04-01 16:16 ` Peter Maydell
2011-04-01 16:55 ` Michael Roth [this message]
2011-04-01 16:58 ` Peter Maydell
2011-04-01 17:24 ` Michael Roth
2011-04-01 17:01 ` Stefan Hajnoczi
2011-04-01 17:25 ` Michael Roth
2011-04-02 13:48 ` Stefan Hajnoczi
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=4D96038B.3020703@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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.