linux-kernel - Re: linux-next: Tree for Dec 12

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:	Fri, 12 Dec 2014 14:56:23 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Valentin Rothberg <valentinrothberg@...il.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andy Lutomirski <luto@...capital.net>,
	Josh Triplett <josh@...htriplett.org>
Subject: Re: linux-next: Tree for Dec 12

On Fri, 12 Dec 2014 23:36:37 +0100 Paul Bolle <pebolle@...cali.nl> wrote:

> On Fri, 2014-12-12 at 13:57 -0800, Andrew Morton wrote:
> > On Fri, 12 Dec 2014 11:31:56 +0100 Paul Bolle <pebolle@...cali.nl> wrote:
> 
> > > I won't be bothering (Andrew and) you again about this. Unless sorting
> > > this out takes rather long, that is.
> > 
> > Is there some problem with the current mainline 3.19 code?
> 
> The problem I noticed is with next-20141212. For some reason - Stephen
> appears to not know exactly why - it ended up with a Kconfig entry for
> INIT_FALLBACK without any actually users of that Kconfig symbol.

How'd that happen? 
http://ozlabs.org/~akpm/mmots/broken-out/init-remove-config_init_fallback.patch
removes all mention of CONFIG_INIT_FALLBACK?

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