From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Dan Carpenter <dan.carpenter@oracle.com>,
Andy Whitcroft <apw@canonical.com>
Subject: [PATCH 0/2] checkpatch: Add --strict macro argument tests
Date: Mon, 12 Sep 2016 22:43:01 -0700 [thread overview]
Message-ID: <cover.1473744906.git.joe@perches.com> (raw)
This is rather better than the first submission.
I think this is acceptable and doesn't need to be RFC.
Joe Perches (2):
checkpatch: Add --strict test for macro argument reuse
checkpatch: Add --strict test for precedence challenged macro arguments
scripts/checkpatch.pl | 50 ++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 42 insertions(+), 8 deletions(-)
--
2.10.0.rc2.1.g053435c
next reply other threads:[~2016-09-13 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 5:43 Joe Perches [this message]
2016-09-13 5:43 ` [PATCH 1/2] checkpatch: Add --strict test for macro argument reuse Joe Perches
2016-09-13 5:43 ` [PATCH 2/2] checkpatch: Add --strict test for precedence challenged macro arguments Joe Perches
2016-09-13 5:53 ` [PATCH V2] " 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=cover.1473744906.git.joe@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=julia.lawall@lip6.fr \
--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 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.