linux-kernel - Re: update checkpatch.pl to version 0.19

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]

Message-ID: <ada3anma9gc.fsf@cisco.com>
Date:	Mon, 09 Jun 2008 08:56:19 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: update checkpatch.pl to version 0.19

 > The issue I have is I have a comprehensive test suite which is kept in
 > lock step with checkpatch itself, all in my own tree.  Now that is just
 > noise for mainline.  What I want to be able to do is keep that in lock
 > step with developments in my tree, but not merge it upstream.  So far
 > I've not found a workable solution with git for that.

>From my naive point of view: why wouldn't we want a test suite upstream,
if one is already written?

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