linux-kernel - Re: Conditionals for development tests and output

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:	Sat, 2 Jun 2007 10:48:21 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Christoph Lameter <clameter@....com>, linux-kernel@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>, Dave Jones <davej@...hat.com>
Subject: Re: Conditionals for development tests and output

On Sat, 2 Jun 2007 16:43:48 +0200 Adrian Bunk <bunk@...sta.de> wrote:

> And your approach could easily result in code paths never tested in 
> -mm or -rc kernels exploding in the actual release.

yep, we need to ensure that DEVELKERNEL gets turned off a few weeks
before final release.
-
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/