From: Andy Whitcroft <apw@canonical.com>
To: Sylvestre Ledru <sylvestre.ledru@scilab.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Daniel Walker <dwalker@fifo99.com>, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: Usage of checkpatch.pl for other projects
Date: Tue, 17 Aug 2010 17:01:23 +0100 [thread overview]
Message-ID: <20100817160123.GL6193@shadowen.org> (raw)
In-Reply-To: <1269337074.12129.4674.camel@korcula.inria.fr>
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
next prev parent reply other threads:[~2010-08-17 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:37 Usage of checkpatch.pl for other projects Sylvestre Ledru
2010-08-17 16:01 ` Andy Whitcroft [this message]
2010-08-17 16:16 ` Sylvestre Ledru
2010-08-17 16:32 ` Joe Perches
2010-08-22 20:50 ` Sylvestre Ledru
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 8:35 Sylvestre Ledru
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=20100817160123.GL6193@shadowen.org \
--to=apw@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=dwalker@fifo99.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvestre.ledru@scilab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox