From: Michal Marek <mmarek@suse.cz>
To: Nicolas Palix <npalix@diku.dk>
Cc: Julia Lawall <julia@diku.dk>,
Gilles Muller <Gilles.Muller@lip6.fr>,
cocci@diku.dk, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 00/18] Add new semantic patches and reorganize existing ones
Date: Tue, 31 Aug 2010 12:22:39 +0200 [thread overview]
Message-ID: <20100831102239.GA18142@sepie.suse.cz> (raw)
In-Reply-To: <1282664352-15882-1-git-send-email-npalix@diku.dk>
On Tue, Aug 24, 2010 at 05:38:54PM +0200, Nicolas Palix wrote:
> The following series adds new semantic patches (SPs) in scripts/coccinelle.
> Existing SPs are reorganized accordingly.
>
> Nicolas Palix (18):
> Coccinelle: Add null/eno.cocci
> Coccinelle: Add null/kmerr.cocci
> Coccinelle: Move deref_null.cocci to a more appropriate directory
> Coccinelle: Add locks/call_kern.cocci
> Coccinelle: Add locks/double_lock.cocci
> Coccinelle: Add locks/mini_lock.cocci
> Coccinelle: Add iterators/fen.cocci
> Coccinelle: Add iterators/itnull.cocci
> Coccinelle: Add iterators/list_entry_update.cocci
> Coccinelle: Add free/kfree.cocci
> Coccinelle: Add api/kstrdup.cocci
> Coccinelle: Add api/memdup.cocci
> Coccinelle: Add api/memdup_user
> Coccinelle: Move err_cast.cocci to the api directory
> Coccinelle: Move resource_size.cocci to the api directory
> Coccinelle: Move alloc directory into api directory
> Coccinelle: Add misc/doubleinit.cocci
> Coccinelle: Add misc/ifcol.cocci
Applied, thanks.
Michal
prev parent reply other threads:[~2010-08-31 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 15:38 Nicolas Palix
2010-08-24 15:38 ` [PATCH 01/18] Coccinelle: Add null/eno.cocci Nicolas Palix
2010-08-24 15:38 ` [PATCH 02/18] Coccinelle: Add null/kmerr.cocci Nicolas Palix
2010-08-24 15:38 ` [PATCH 03/18] Coccinelle: Move deref_null.cocci to a more appropriate directory Nicolas Palix
2010-08-24 15:38 ` [PATCH 04/18] Coccinelle: Add locks/call_kern.cocci Nicolas Palix
2010-08-24 15:38 ` [PATCH 05/18] Coccinelle: Add locks/double_lock.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 06/18] Coccinelle: Add locks/mini_lock.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 07/18] Coccinelle: Add iterators/fen.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 08/18] Coccinelle: Add iterators/itnull.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 09/18] Coccinelle: Add iterators/list_entry_update.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 10/18] Coccinelle: Add free/kfree.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 11/18] Coccinelle: Add api/kstrdup.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 12/18] Coccinelle: Add api/memdup.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 13/18] Coccinelle: Add api/memdup_user Nicolas Palix
2010-08-24 15:39 ` [PATCH 14/18] Coccinelle: Move err_cast.cocci to the api directory Nicolas Palix
2010-08-24 15:39 ` [PATCH 15/18] Coccinelle: Move resource_size.cocci " Nicolas Palix
2010-08-24 15:39 ` [PATCH 16/18] Coccinelle: Move alloc directory into " Nicolas Palix
2010-08-24 15:39 ` [PATCH 17/18] Coccinelle: Add misc/doubleinit.cocci Nicolas Palix
2010-08-24 15:39 ` [PATCH 18/18] Coccinelle: Add misc/ifcol.cocci Nicolas Palix
2010-08-31 10:22 ` Michal Marek [this message]
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=20100831102239.GA18142@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix@diku.dk \
/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®