From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] scripts/checkpatch.pl: Enforce multiline comment syntax
Date: Mon, 13 Aug 2018 08:26:27 +0200 [thread overview]
Message-ID: <e760a064-47b4-5e11-425f-8bad9ba3efbb@redhat.com> (raw)
In-Reply-To: <20180809160011.17225-1-peter.maydell@linaro.org>
On 08/09/2018 06:00 PM, Peter Maydell wrote:
> We now require Linux-kernel-style multiline comments:
> /*
> * line one
> * line two
> */
>
> Enforce this in checkpatch.pl, by backporting the relevant
> parts of the Linux kernel's checkpatch.pl. (The only changes
> needed are that Linux's checkpatch.pl WARN() function takes
> an extra argument that ours does not.)
>
> The kernel's checkpatch does not enforce "leading /* on
> a line of its own, so that part is unique to QEMU's checkpatch.
>
> Sample warning output:
>
> WARNING: Block comments use a leading /* on a separate line
> #34: FILE: hw/intc/arm_gicv3_common.c:39:
> + /* Older versions of QEMU had a bug in the handling of state save/restore
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> I'm still not used to the leeading-/*-on-it's-own style,
> so having checkpatch catch my lapses is handy...
>
> I used WARN level severity mostly because Linux does.
> ---
> scripts/checkpatch.pl | 48 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
Acked-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2018-08-13 6:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 16:00 [Qemu-devel] [PATCH] scripts/checkpatch.pl: Enforce multiline comment syntax Peter Maydell
2018-08-09 16:43 ` Paolo Bonzini
2018-08-09 17:03 ` Peter Maydell
2018-08-10 8:34 ` Paolo Bonzini
2018-08-10 9:10 ` Peter Maydell
2018-08-10 12:45 ` Paolo Bonzini
2018-08-10 12:53 ` Peter Maydell
2018-08-10 17:06 ` Paolo Bonzini
2018-08-13 6:18 ` Thomas Huth
2018-08-13 8:01 ` Paolo Bonzini
2018-08-10 9:41 ` Markus Armbruster
2018-08-10 12:44 ` Paolo Bonzini
2018-08-10 13:19 ` Markus Armbruster
2018-08-10 6:22 ` Markus Armbruster
2018-08-10 9:07 ` Peter Maydell
2018-08-10 12:08 ` Markus Armbruster
2018-08-13 6:26 ` Thomas Huth [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=e760a064-47b4-5e11-425f-8bad9ba3efbb@redhat.com \
--to=thuth@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).