From: Joe Perches <joe@perches.com>
To: Graeme Russ <graeme.russ@gmail.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
U-Boot Users <u-boot@lists.denx.de>
Subject: Re: Expanding checkpatch for non-linux (specifically U-Boot) use
Date: Sun, 24 Apr 2011 23:32:36 -0700 [thread overview]
Message-ID: <1303713156.1745.38.camel@Joe-Laptop> (raw)
In-Reply-To: <4DB51333.7060809@gmail.com>
On Mon, 2011-04-25 at 16:22 +1000, Graeme Russ wrote:
> I like this - And checkpatch.pl could set the default options for 'Linux
> flavour' so Linux would not need a .conf file :)
>
> BUT - The question still remains - Will patches for obviously non-Linux
> related 'features' of checkpatch be welcomed and incorporated into checkpatch?
I don't see a problem with it, I'd ack patches if the
design and implementation is reasonably clean, but it's
not really for me to decide.
Another possibility is to keep all the uboot specific
stuff in a separate .pl file and let that file be
executed by checkpatch. Modularity and such is good.
Andy Whitcroft is the nominal maintainer, but he hasn't
been particularly active with checkpatch for awhile as
his real job seems to keep him busy.
Andrew Morton has been overseeing most of the trivial
style maintenance patches to checkpatch for the last
year or so.
cheers, Joe
next prev parent reply other threads:[~2011-04-25 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 5:36 Expanding checkpatch for non-linux (specifically U-Boot) use Graeme Russ
2011-04-25 6:02 ` Joe Perches
2011-04-25 6:22 ` Graeme Russ
2011-04-25 6:32 ` Joe Perches [this message]
2011-04-26 0:43 ` [RFC PATCH] checkpatch.pl: Add ability to ignore various messages Joe Perches
2011-06-09 19:26 ` Joe Perches
2011-06-09 19:40 ` [U-Boot] " Mike Frysinger
2011-07-27 21:17 ` Wolfgang Denk
2011-07-27 22:10 ` Joe Perches
2011-08-24 21:25 ` Wolfgang Denk
2011-08-24 21:33 ` Joe Perches
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=1303713156.1745.38.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=graeme.russ@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=u-boot@lists.denx.de \
/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