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: <20140114140117.bff3db92027fea9eb6f2af7f@linux-foundation.org>
Date:	Tue, 14 Jan 2014 14:01:17 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Philipp Hachtmann <phacht@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	qiuxishi@...wei.com, dhowells@...hat.com, daeseok.youn@...il.com,
	liuj97@...il.com, yinghai@...nel.org, zhangyanfei@...fujitsu.com,
	santosh.shilimkar@...com, grygorii.strashko@...com,
	tangchen@...fujitsu.com
Subject: Re: [PATCH V3 2/2] mm/memblock: Add support for excluded memory
 areas

On Tue, 14 Jan 2014 10:42:53 +0100 Philipp Hachtmann <phacht@...ux.vnet.ibm.com> wrote:

> Am Mon, 13 Jan 2014 16:36:20 -0800
> schrieb Andrew Morton <akpm@...ux-foundation.org>:
> 
> > Patch is big.  I'll toss this in for some testing but it does look too
> > large and late for 3.14.  How will this affect your s390 development?
> 
> It is needed for s390 bootmem -> memblock transition. The s390 dump
> mechanisms cannot be switched to memblock (from using something s390
> specific called memory_chunk) without the nomap list.
> I'm also working on another enhancement on s390 that will rely on a
> clean transition to memblock.
> 
> I have written and tested the stuff on top of our local development
> tree. And then realised that it does not fit the linux-next tree. So I
> converted it to fit linux-next and posted it. Have to maintain two
> versions now. 

So at 3.14-rc1 everything will come good - get the review issues sorted
out, add the patch to your tree (and hence linux-next).
--
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