From: Nicolas Palix <npalix@diku.dk>
To: Randy Dunlap <rdunlap@xenotime.net>,
Roland Dreier <rdreier@cisco.com>, Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>,
Julia Lawall <julia@diku.dk>,
Gilles Muller <Gilles.Muller@lip6.fr>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
cocci@diku.dk, Wolfram Sang <w.sang@pengutronix.de>
Cc: Kernel Janitors <kernel-janitors@vger.kernel.org>,
Nicolas Palix <npalix@diku.dk>
Subject: [PATCH 0/4] Add a Coccinelle front-end script
Date: Mon, 10 May 2010 16:24:23 +0000 [thread overview]
Message-ID: <1273508667-5152-1-git-send-email-npalix@diku.dk> (raw)
In-Reply-To: <1273508351-4998-1-git-send-email-npalix@diku.dk>
New targets are added (coccicheck-<mode>) to call the 'coccinelle.sh' front-end
in the 'scripts' directory with the <mode> argument.
Four modes are defined: report, patch, context, and org.
'report' mode generates a list in the following format:
file:line:column-column: message
'patch' mode proposes a generic fix, when possible.
'context' mode highlights lines of interest and their context
in a diff-like style.
'org' mode generates a report in the Org mode format of Emacs.
Three semantic patches, with a low rate of false positives, are also
included. Other semantic patches will be provided later. Note that a
semantic patch does not need to define all four modes. As many semantic
patches may be proposed later, they are organized under sub-directories
of 'scripts/coccinelle/'.
We add a reference to the tool in the proposed changelog because it will
make the changelog easier to understand for someone who is not aware of
the tool.
To apply a single semantic patch, the user can define the COCCI environment
variable which gives the path to the semantic patch.
Nicolas Palix (4):
Add targets to use the Coccinelle checker
Add scripts/coccinelle/drop_kmalloc_cast.cocci
Add scripts/coccinelle/kzalloc-simple.cocci
Add scripts/coccinelle/resource_size.cocci
MAINTAINERS | 10 +++
Makefile | 20 +++++-
scripts/coccinelle.sh | 28 ++++++++
scripts/coccinelle/drop_kmalloc_cast.cocci | 68 ++++++++++++++++++++
scripts/coccinelle/kzalloc-simple.cocci | 83 ++++++++++++++++++++++++
scripts/coccinelle/resource_size.cocci | 94 ++++++++++++++++++++++++++++
6 files changed, 301 insertions(+), 2 deletions(-)
create mode 100755 scripts/coccinelle.sh
create mode 100644 scripts/coccinelle/drop_kmalloc_cast.cocci
create mode 100644 scripts/coccinelle/kzalloc-simple.cocci
create mode 100644 scripts/coccinelle/resource_size.cocci
next prev parent reply other threads:[~2010-05-10 16:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 16:19 [PATCH 0/4] Add a Coccinelle front-end script Nicolas Palix
2010-05-10 16:24 ` Nicolas Palix [this message]
2010-05-10 16:24 ` [PATCH 1/4] Add targets to use the Coccinelle checker Nicolas Palix
2010-05-12 6:42 ` Américo Wang
2010-05-28 7:04 ` Joerg Roedel
2010-06-03 9:50 ` Michal Marek
2010-06-03 10:23 ` Sam Ravnborg
2010-06-04 9:56 ` Nicolas Palix
2010-06-04 10:38 ` Sam Ravnborg
2010-05-10 16:24 ` [PATCH 2/4] Add scripts/coccinelle/drop_kmalloc_cast.cocci Nicolas Palix
2010-05-10 16:24 ` [PATCH 3/4] Add scripts/coccinelle/kzalloc-simple.cocci Nicolas Palix
2010-06-03 9:51 ` Michal Marek
2010-06-03 10:11 ` Nicolas Palix
2010-05-10 16:24 ` [PATCH 4/4] Add scripts/coccinelle/resource_size.cocci Nicolas Palix
2010-05-10 16:52 ` Pekka Enberg
2010-05-27 11:48 ` Nicolas Palix
2010-05-11 2:14 ` [PATCH 0/4] Add a Coccinelle front-end script Andy Isaacson
2010-05-17 9:31 ` Wolfram Sang
2010-05-28 7:09 ` Joerg Roedel
2010-05-28 7:25 ` Wolfram Sang
2010-05-28 7:31 ` Julia Lawall
2010-05-28 7:39 ` walter harms
2010-05-28 9:15 ` Joerg Roedel
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=1273508667-5152-1-git-send-email-npalix@diku.dk \
--to=npalix@diku.dk \
--cc=Gilles.Muller@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=cocci@diku.dk \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdreier@cisco.com \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.org \
--cc=w.sang@pengutronix.de \
/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