[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100817160123.GL6193@shadowen.org>
Date: Tue, 17 Aug 2010 17:01:23 +0100
From: Andy Whitcroft <apw@...onical.com>
To: Sylvestre Ledru <sylvestre.ledru@...lab.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Daniel Walker <dwalker@...o99.com>,
Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org
Subject: Re: Usage of checkpatch.pl for other projects
On Tue, Mar 23, 2010 at 10:37:54AM +0100, Sylvestre Ledru wrote:
> Hello,
>
> I saw the very interesting presentation of Greg at the last FOSDEM where
> he explained how to write a patch of the kernel.
>
> During his presentation, he presented the script checkpatch.pl which
> checks the coding style of a patch / file.
>
> For a while, I have been looking for such script which can check the
> compliance of a source code against a coding policy.
>
> Obviously, the coding style of my project is not exactly the same as he
> Kernel one.
>
> Therefor, I would like to know if there is any plan of making a
> dedicated project of this piece of software to allow usage of it for
> other projects.
> If it is not the case, is it possible to contribute to change the
> behavior of the policy check (of course, disable by default for kernel
> hackers) ?
An interesting question. Cirtianly most of its behaviour is kernel
centric. The source kinda lives outside the kernel with its tests
so could be consumed by other projects (though we do keep a copy in the
kernel tree too). If changes could be conditional on the project I
could see it being possible. What sort of differences are you thinking
about.
-apw
--
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