From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, joe@perches.com
Subject: [folded-merged] checkpatch-add-check-for-sscanf-without-return-use-v2.patch removed from -mm tree
Date: Tue, 12 Nov 2013 14:41:19 -0800 [thread overview]
Message-ID: <5282ae8f.DkdCgO2+EhrMYNjY%akpm@linux-foundation.org> (raw)
Subject: [folded-merged] checkpatch-add-check-for-sscanf-without-return-use-v2.patch removed from -mm tree
To: joe@perches.com,mm-commits@vger.kernel.org
From: akpm@linux-foundation.org
Date: Tue, 12 Nov 2013 14:41:19 -0800
The patch titled
Subject: checkpatch-add-check-for-sscanf-without-return-use-v2
has been removed from the -mm tree. Its filename was
checkpatch-add-check-for-sscanf-without-return-use-v2.patch
This patch was dropped because it was folded into checkpatch-add-check-for-sscanf-without-return-use.patch
------------------------------------------------------
From: Joe Perches <joe@perches.com>
Subject: checkpatch-add-check-for-sscanf-without-return-use-v2
V2: Use the $Compare variable instead of just == or !=
There are some tests that use < and >
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/checkpatch.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN scripts/checkpatch.pl~checkpatch-add-check-for-sscanf-without-return-use-v2 scripts/checkpatch.pl
--- a/scripts/checkpatch.pl~checkpatch-add-check-for-sscanf-without-return-use-v2
+++ a/scripts/checkpatch.pl
@@ -4019,8 +4019,8 @@ sub process {
defined $stat &&
$stat =~ /\bsscanf\b/ &&
($stat !~ /$Ident\s*=\s*sscanf\s*$balanced_parens/ &&
- $stat !~ /\bsscanf\s*$balanced_parens\s*(?:==|\!=)/ &&
- $stat !~ /(?:==|\!=)\s*\bsscanf\s*$balanced_parens/)) {
+ $stat !~ /\bsscanf\s*$balanced_parens\s*(?:$Compare)/ &&
+ $stat !~ /(?:$Compare)\s*\bsscanf\s*$balanced_parens/)) {
my $lc = $stat =~ tr@\n@@;
$lc = $lc + $linenr;
my $stat_real = raw_line($linenr, 0);
_
Patches currently in -mm which might be from joe@perches.com are
origin.patch
ocfs2-convert-use-of-typedef-ctl_table-to-struct-ctl_table.patch
ksm-remove-redundant-__gfp_zero-from-kcalloc.patch
printk-report-console-names-during-cut-over.patch
kernel-printk-printkc-convert-to-pr_foo.patch
vsprintf-check-real-user-group-id-for-%pk.patch
printkc-comments-should-refer-to-proc-vmcore-instead-of-proc-vmcoreinfo.patch
checkpatch-report-missing-spaces-around-trigraphs-with-strict.patch
checkpatch-extend-camelcase-types-and-ignore-existing-camelcase-uses-in-a-patch.patch
checkpatch-update-seq_foo-tests.patch
checkpatch-find-camelcase-definitions-of-struct-union-enum.patch
checkpatch-add-test-for-defines-of-arch_has_foo.patch
checkpatch-add-rules-to-check-init-attribute-and-const-defects.patch
checkpatch-make-the-memory-barrier-test-noisier.patch
checkpatchpl-check-for-the-fsf-mailing-address.patch
checkpatch-improve-return-is-not-a-function-test.patch
checkpatch-dont-require-kernel-style-__attribute__-shortcuts-in-uapi-paths.patch
checkpatch-add-check-for-sscanf-without-return-use.patch
drivers-rtc-rtc-puv3c-use-dev_dbg-instead-of-pr_debug.patch
drivers-rtc-rtc-pl030c-use-devm_kzalloc-instead-of-kmalloc.patch
kernel-modulec-use-pr_foo.patch
reply other threads:[~2013-11-12 22:41 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=5282ae8f.DkdCgO2+EhrMYNjY%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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 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.