From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] checkpatch: Check for use of disallowed macros
Date: Thu, 18 Dec 2014 22:15:28 +0100 [thread overview]
Message-ID: <87ppbg64nj.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <1418383004.18092.46.camel@perches.com> (Joe Perches's message of "Fri, 12 Dec 2014 03:16:44 -0800")
On Fri, Dec 12 2014, Joe Perches <joe@perches.com> wrote:
> On Fri, 2014-12-12 at 11:51 +0100, Rasmus Villemoes wrote:
>> Since fe7c36c7 ("Makefile: Build with -Werror=date-time if the
>> compiler supports it"), use of __DATE__, __TIME__, __TIMESTAMP__ has
>> been disallowed. This hasn't prevented a few new users from creeping
>> in. Make checkpatch complain.
>> +
>> +# Use of __DATE__, __TIME__, __TIMESTAMP__ is not allowed
>> + if ($line =~ m/\b__(?:DATE|TIME|TIMESTAMP)__\b/) {
>> + ERROR("DATETIME", "Do not use the macros __DATE__, __TIME__ and __TIMESTAMP__\n" . $herecurr)
>
> I'd probably add that adjacent to the existing __FUNCTION__
> test near line 5000 and make the test show the specific macro
> used.
Yeah, that makes sense. I didn't really know where to put it.
> Maybe add __LINE__ and __FILE__ as a separate --strict test too.
Are those also disallowed, or is it just that new users shouldn't be
added?
> Also the error message should should show the specific macro and
> if __DATE__ and __TIME__ are on the same line, the error should
> be emitted twice.
>
> Maybe:
> while ($line =~ /\b(__(?:DATE|TIME|TIMESTAMP)__)\b/g) {
> ERROR("DATETIME",
> "Do not use the $1 macro\n" . $herecurr);
> }
Looks good to me. I could resend, but can't really claim
authorship. Joe, mind taking it from here?
Rasmus
next prev parent reply other threads:[~2014-12-18 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:51 Rasmus Villemoes
2014-12-12 10:51 ` [PATCH 2/3] staging: unisys: remove leftover __DATE__ Rasmus Villemoes
2014-12-12 10:51 ` [PATCH 3/3] ACPICA: Remove use of __DATE__ macro Rasmus Villemoes
2015-01-05 8:47 ` Zheng, Lv
2015-01-05 10:26 ` Rasmus Villemoes
2015-01-06 0:30 ` Zheng, Lv
2015-01-06 19:36 ` [Devel] " David E. Box
2015-01-13 2:33 ` Zheng, Lv
2015-01-13 5:42 ` Zheng, Lv
2014-12-12 11:16 ` [PATCH 1/3] checkpatch: Check for use of disallowed macros Joe Perches
2014-12-18 21:15 ` Rasmus Villemoes [this message]
2014-12-18 21:26 ` Joe Perches
2014-12-18 22:17 ` checkpatch: Emit an error when using predefined timestamp macros Joe Perches
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=87ppbg64nj.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=joe@perches.com \
--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
Powered by JetHome