linux-kernel - Re: Expanding checkpatch for non-linux (specifically U-Boot) use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 24 Apr 2011 23:32:36 -0700
From:	Joe Perches <joe@...ches.com>
To:	Graeme Russ <graeme.russ@...il.com>
Cc:	Andy Whitcroft <apw@...onical.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	U-Boot Users <u-boot@...ts.denx.de>
Subject: Re: Expanding checkpatch for non-linux (specifically U-Boot) use

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

--
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/