linux-kernel - Re: linux-next: Tree for November 23

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

Rusty Russell wrote:
> On Tue, 24 Nov 2009 05:45:10 am Randy Dunlap wrote:
>> On Mon, 23 Nov 2009 18:52:32 +1100 Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Changes since 20091120:
>>
>> Hey rr,
>>
>> This patch "param\:remove-useless-writable-charp.patch" has several typos
>> that cause build errors in drivers/staging/.  I sent patches for these errors
>> to gregkh but he couldn't apply them.  Please build STAGING (drivers/staging/)
>> crap along with other build testing when you make changes.
> 
> Hi Randy,
> 
>     Fixed.  And I guess linux-next doesn't build staging?  Seems a fair call,
> I should have done so.

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.  :(

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