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: <4B0B1CCA.7070500@oracle.com>
Date:	Mon, 23 Nov 2009 15:37:46 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Randy Dunlap <randy.dunlap@...cle.com>,
	Rusty Russell <rusty@...tcorp.com.au>, gregkh@...e.de,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for November 23

Stephen Rothwell wrote:
> Hi Randy,
> 
> On Mon, 23 Nov 2009 15:04:39 -0800 Randy Dunlap <randy.dunlap@...cle.com> wrote:
>> I decided to check on linux-next (only checked x86_64 allmodconfig),
>> and viola:
>>
>> CONFIG_STAGING=y
>> CONFIG_STAGING_EXCLUDE_BUILD=y
>>
>> That is just too helpful.  :(
> 
> The Kconfig was deliberately done so that the all{no,yes,mod}config
> builds don't build the staging stuff.  You need to explictly ask for it.
> Otherwise I would spend all my time reporting/fixing errors and warnings
> in linux-next.
> 

no, you should just drop it after one build error.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ