linux-kernel - Re: linux-next: build failure after merge of the memblock tree

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: <CAOS58YOSp6VOJ6WCOyYf3KEJ=_p9ZG4LXmK8YiDgn4Y7DbVHKA@mail.gmail.com>
Date:	Wed, 7 Dec 2011 13:30:44 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the memblock tree

Hello,

On Wed, Dec 7, 2011 at 12:54 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Caused by commit 9d0d131f9f6d ("memblock: Kill early_node_map[]") which
>> seems to have misspelled CONFIG_HAVE_MEMBLOCK_NODE_MAP as
>> CONFIG_MEMBLOCK_HAVE_NODE_MAP in include/linux/mmzone.h.
>>
>> I have dropped the memblock tree for today - we can try again tomorrow.
>
> Ping?

Still trying to restore my cross build setup. I think I will be able
to send update series later today.

Thanks.

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