linux-kernel - Re: [PATCH 0/8] Create and populate toplevel tests/ for kernel tests

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:	Tue, 12 Feb 2008 13:34:11 -0800
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Christoph Hellwig <hch@...radead.org>, ananth@...ibm.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	mingo@...e.hu, ak@...e.de, sam@...nborg.org
Subject: Re: [PATCH 0/8] Create and populate toplevel tests/ for kernel tests

Andrew Morton wrote:
> On Tue, 12 Feb 2008 11:44:52 -0500
> Christoph Hellwig <hch@...radead.org> wrote:
> 
>> On Mon, Feb 11, 2008 at 04:14:52PM +0530, Ananth N Mavinakayanahalli wrote:
>>> The following series of patches create and populate the toplevel tests/
>>> directory. This will henceforth be the place where all in-kernel tests
>>> live.
>>>
>>> All patches against 2.6.25-rc1 and are just code movement without any
>>> change in functionality.
>> ACK to patches 1-7, and I agree with Ingo that the x86-specific test
>> should stay under arch/x86.
> 
> OK.  But now is basically the worst time for me (or anyone else) to merge
> large code-motion changes like this, because they need to be carried for
> two months or more.
> 

alternatively, since it's just code motion and nothing more, it could just
be done in 2.6.25-rc; in fact doing motion patches in the -rc2 window makes sense to me,
that's the point where all external trees are the smallest, and it should be provably
the same result.. so safe.
--
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/