From: Wolfram Sang <w.sang@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH] checkpatch: fix false positive on __initconst
Date: Mon, 16 Nov 2009 15:02:35 +0100 [thread overview]
Message-ID: <20091116140220.GC30609@pengutronix.de> (raw)
In-Reply-To: <1255945754-2160-1-git-send-email-w.sang@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
ping
On Mon, Oct 19, 2009 at 11:49:14AM +0200, Wolfram Sang wrote:
> checkpatch falsely complained about '__initconst' because it thought the
> 'const' needed a space before. Fix this by changing the list of attributes:
>
> - add '__initconst'
> - force plain 'init' to contain a word-boundary at the end
>
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> Cc: Andy Whitcroft <apw@shadowen.org>
> ---
>
> Not entirely sure if adding the word boundary may cause a side-effect which I
> overlooked. A few more eyes on this would be great.
>
> scripts/checkpatch.pl | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 87bbb8b..0a47a1f 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -142,11 +142,14 @@ our $Sparse = qr{
> __kprobes|
> __ref
> }x;
> +
> +# Notes to $Attribute:
> +# We need \b after 'init' otherwise 'initconst' will cause a false positive in a check
> our $Attribute = qr{
> const|
> __read_mostly|
> __kprobes|
> - __(?:mem|cpu|dev|)(?:initdata|init)|
> + __(?:mem|cpu|dev|)(?:initdata|initconst|init\b)|
> ____cacheline_aligned|
> ____cacheline_aligned_in_smp|
> ____cacheline_internodealigned_in_smp|
> --
> 1.6.3.3
>
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-11-16 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 9:49 Wolfram Sang
2009-11-16 14:02 ` Wolfram Sang [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=20091116140220.GC30609@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®