From: andi@firstfloor.org (Andi Kleen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] checkpatch: Add test for positional misuse of section specifiers like __initdata
Date: Sat, 31 Aug 2013 16:31:23 +0200 [thread overview]
Message-ID: <20130831143123.GC19750@two.firstfloor.org> (raw)
In-Reply-To: <1377655732.3619.19.camel@joe-AO722>
> A similar patch was suggested by Andi Kleen
> https://lkml.org/lkml/2013/8/5/648
My patch checked for const <-> initdata / non const initconst mistakes.
I don't think your patch does that?
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <khali@linux-fr.org>,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] checkpatch: Add test for positional misuse of section specifiers like __initdata
Date: Sat, 31 Aug 2013 16:31:23 +0200 [thread overview]
Message-ID: <20130831143123.GC19750@two.firstfloor.org> (raw)
In-Reply-To: <1377655732.3619.19.camel@joe-AO722>
> A similar patch was suggested by Andi Kleen
> https://lkml.org/lkml/2013/8/5/648
My patch checked for const <-> initdata / non const initconst mistakes.
I don't think your patch does that?
-Andi
next prev parent reply other threads:[~2013-08-31 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 2:08 [PATCH] checkpatch: Add test for positional misuse of section specifiers like __initdata Joe Perches
2013-08-28 2:08 ` Joe Perches
2013-08-31 14:31 ` Andi Kleen [this message]
2013-08-31 14:31 ` Andi Kleen
2013-08-31 16:04 ` Joe Perches
2013-08-31 16:04 ` Joe Perches
2013-08-31 16:41 ` Andi Kleen
2013-08-31 16:41 ` Andi Kleen
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=20130831143123.GC19750@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-arm-kernel@lists.infradead.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 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.