From: akpm@linux-foundation.org
To: joe@perches.com, apw@canonical.com, mm-commits@vger.kernel.org
Subject: [merged] checkpatch-find-hex-constants-as-a-single-ident.patch removed from -mm tree
Date: Tue, 18 Dec 2012 12:07:03 -0800 [thread overview]
Message-ID: <20121218200704.172BC200057@hpza10.eem.corp.google.com> (raw)
The patch titled
Subject: checkpatch: find hex constants as a single IDENT
has been removed from the -mm tree. Its filename was
checkpatch-find-hex-constants-as-a-single-ident.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Joe Perches <joe@perches.com>
Subject: checkpatch: find hex constants as a single IDENT
Hexadecimal values are current found in 2 parts. A hex constant like
0x123456abcdef is found as 0 and then x123456abcdef and later coalesced.
Instead, reverse the order of the 2 searches in $Constant to find 0x
first, then 0 so that the entire hex constant is found all at once.
Signed-off-by: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN scripts/checkpatch.pl~checkpatch-find-hex-constants-as-a-single-ident scripts/checkpatch.pl
--- a/scripts/checkpatch.pl~checkpatch-find-hex-constants-as-a-single-ident
+++ a/scripts/checkpatch.pl
@@ -230,7 +230,7 @@ our $Inline = qr{inline|__always_inline|
our $Member = qr{->$Ident|\.$Ident|\[[^]]*\]};
our $Lval = qr{$Ident(?:$Member)*};
-our $Constant = qr{(?i:(?:[0-9]+|0x[0-9a-f]+)[ul]*)};
+our $Constant = qr{(?i:(?:0x[0-9a-f]+|[0-9]+)[ul]*)};
our $Assignment = qr{(?:\*\=|/=|%=|\+=|-=|<<=|>>=|&=|\^=|\|=|=)};
our $Compare = qr{<=|>=|==|!=|<|>};
our $Operators = qr{
_
Patches currently in -mm which might be from joe@perches.com are
origin.patch
linux-next.patch
reply other threads:[~2012-12-18 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121218200704.172BC200057@hpza10.eem.corp.google.com \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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