From: Gregory.Dietsche@cuw.edu
To: julia@diku.dk, Gilles.Muller@lip6.fr, npalix.work@gmail.com,
mmarek@suse.cz
Cc: rdunlap@xenotime.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cocci@diku.dk,
Greg Dietsche <Gregory.Dietsche@cuw.edu>
Subject: [RESEND 1/3] coccinelle.txt: add overview section
Date: Sat, 5 Nov 2011 21:14:11 -0500 [thread overview]
Message-ID: <1320545653-28249-2-git-send-email-Gregory.Dietsche@cuw.edu> (raw)
In-Reply-To: <1320545653-28249-1-git-send-email-Gregory.Dietsche@cuw.edu>
From: Greg Dietsche <Gregory.Dietsche@cuw.edu>
Add an overview section to the coccinelle documentation.
Signed-off-by: Greg Dietsche <Gregory.Dietsche@cuw.edu>
Signed-off-by: Nicolas Palix <npalix.work@gmail.com>
---
Documentation/coccinelle.txt | 31 +++++++++++++++++++++++++++++++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/Documentation/coccinelle.txt b/Documentation/coccinelle.txt
index 96b6903..9495a4b 100644
--- a/Documentation/coccinelle.txt
+++ b/Documentation/coccinelle.txt
@@ -41,6 +41,37 @@ The semantic patches in the kernel will work best with Coccinelle version
semantic patch code, but any results that are obtained should still be
correct.
+
+ Overview / Quick Start
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+There are two ways to use Coccinelle with the Linux kernel.
+
+1) Coccinelle can be used like sparse (see Documentation/sparse.txt):
+ make C=1 CHECK="scripts/coccicheck"
+ make C=2 CHECK="scripts/coccicheck"
+
+2) Coccinelle can be used via a build target in the kernel's Makefile:
+ make coccicheck
+
+There are a number of optional parameters that can be used with the build target.
+
+ make coccicheck MODE={patch,report,context,org} COCCI=? M=?
+
+MODE:
+ Determines what mode cocci operates in. If no mode is specified
+ then cocci will default to 'chain' mode which will run for each
+ available mode (patch, report, context, org).
+
+COCCI:
+ Process a specific .cocci SmPL script. If this is not set then
+ process all scripts under scripts/coccinelle/
+
+M:
+ Limit cocci to a subset of directories. This is very similar to the
+ way the build system works when building modules.
+
+
Using Coccinelle on the Linux kernel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
1.7.6.4
next prev parent reply other threads:[~2011-11-06 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 2:14 [RESEND 0/3] coccinelle: add parallel execution Gregory.Dietsche
2011-11-06 2:14 ` Gregory.Dietsche [this message]
2011-11-06 18:18 ` [RESEND 1/3] coccinelle.txt: add overview section Julia Lawall
2011-11-06 2:14 ` [RESEND 2/3] coccinelle.txt: add documentation of PARALLEL= flag Gregory.Dietsche
2011-11-06 18:19 ` Julia Lawall
2011-11-06 2:14 ` [RESEND 3/3] coccicheck: add parallel execution Gregory.Dietsche
2011-11-06 18:20 ` Julia Lawall
2011-12-11 20:48 ` Michal Marek
2012-01-12 17:20 ` Greg Dietsche
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=1320545653-28249-2-git-send-email-Gregory.Dietsche@cuw.edu \
--to=gregory.dietsche@cuw.edu \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=julia@diku.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=npalix.work@gmail.com \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®