From: Wolfram Sang <w.sang@pengutronix.de>
To: Nicolas Palix <npalix@diku.dk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
"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
Subject: Re: [PATCH 0/4] Add a Coccinelle front-end script
Date: Tue, 27 Apr 2010 14:50:14 +0200 [thread overview]
Message-ID: <20100427125014.GD1775@pengutronix.de> (raw)
In-Reply-To: <1272316279-12042-1-git-send-email-npalix@diku.dk>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On Mon, Apr 26, 2010 at 11:11:15PM +0200, Nicolas Palix wrote:
> New targets are added (coccicheck-<mode>) to call the spatch 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.
So, as I understood all semantic patches have to support 'org'?
I think this makes submitting slightly more complicated...
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-04-27 12:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 21:11 [PATCH 0/4] Add a Coccinelle front-end script Nicolas Palix
2010-04-26 21:11 ` [PATCH 1/4] Add targets to use the Coccinelle checker Nicolas Palix
2010-04-26 21:37 ` Joe Perches
2010-04-26 22:20 ` Nicolas Palix
2010-04-26 22:20 ` Nicolas Palix
2010-04-26 22:23 ` Randy Dunlap
2010-04-29 17:01 ` Roland Dreier
2010-04-30 21:07 ` Randy Dunlap
2010-04-27 12:40 ` Michal Marek
2010-04-27 13:01 ` Michal Marek
2010-04-27 12:53 ` Wolfram Sang
2010-04-27 20:24 ` Sam Ravnborg
2010-04-27 20:28 ` Sam Ravnborg
2010-04-26 21:11 ` [PATCH 2/4] Add scripts/smpl/drop_kmalloc_cast.cocci Nicolas Palix
2010-04-26 21:11 ` [PATCH 3/4] Add scripts/smpl/kzalloc-simple.cocci Nicolas Palix
2010-04-26 21:11 ` [PATCH 4/4] Add scripts/smpl/resource_size.cocci Nicolas Palix
2010-04-27 12:50 ` Wolfram Sang [this message]
2010-04-27 12:53 ` [PATCH 0/4] Add a Coccinelle front-end script Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2010-05-10 16:19 Nicolas Palix
2010-05-10 16:24 ` Nicolas Palix
2010-05-10 16:24 ` Nicolas Palix
2010-05-11 2:14 ` Andy Isaacson
2010-05-11 2:14 ` Andy Isaacson
2010-05-17 9:31 ` Wolfram Sang
2010-05-17 9:31 ` Wolfram Sang
2010-05-28 7:09 ` Joerg Roedel
2010-05-28 7:09 ` Joerg Roedel
2010-05-28 7:25 ` Wolfram Sang
2010-05-28 7:25 ` Wolfram Sang
2010-05-28 7:31 ` Julia Lawall
2010-05-28 7:31 ` Julia Lawall
2010-05-28 7:39 ` walter harms
2010-05-28 7:39 ` walter harms
2010-05-28 9:15 ` Joerg Roedel
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=20100427125014.GD1775@pengutronix.de \
--to=w.sang@pengutronix.de \
--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=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=npalix@diku.dk \
--cc=sam@ravnborg.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.