[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.1001181220530.14962@ask.diku.dk>
Date: Mon, 18 Jan 2010 12:22:56 +0100 (CET)
From: Julia Lawall <julia@...u.dk>
To: Michal Marek <mmarek@...e.cz>
Cc: Németh Márton <nm127@...email.hu>,
linux-kbuild@...r.kernel.org,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Pekka Enberg <penberg@...helsinki.fi>,
David Miller <davem@...emloft.net>, stefanr@...6.in-berlin.de,
adi@...apodia.org, david.vrabel@....com, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, cocci@...u.dk,
Andrew Morton <akpm@...ux-foundation.org>,
Nicolas Palix <npalix@...u.dk>
Subject: Re: SmPL scripts into build environment?
> Documentation/smpl/$name_of_problem_fixed.cocci? Or maybe better
> scripts/smlp/..., if you are going to add some wrapper that runs the
> semantic patches on the source tree. Or something like that, a dedicated
> subdirectory to store the semantic patches in individual files.
The idea is to make it possible to run them, assuming the user has
installed Coccinelle, so scripts seems better.
> > What do you think the best way would be to introduce some check like this
> > in the build environment?
>
> I've only heard about the tool, I haven't used it yet. Does it need to
> preprocess and parse source files like sparse does, or can it check C
> files without expanding macros and includes?
It doesn't need to preprocess the source files.
thanks,
julia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists