linux-kernel - Re: linux-next: status 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: <20130828122809.GC18348@mtj.dyndns.org>
Date:	Wed, 28 Aug 2013 08:28:09 -0400
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: status of the memblock tree

Hey, Stephen.

On Wed, Aug 28, 2013 at 04:34:59PM +1000, Stephen Rothwell wrote:
> I was wondering if the memblock tree needs to exist any more.  The last
> commit to it was in December 2011 and was merged into Linus' tree during
> the v3.3 merge window.

After the rewrite was complete, the tree was never used.  I think it
can be put to rest now.  Ingo is routing all memblock changes now.

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/