linux-kernel - Re: openrisc: Consolidate setup to use memblock instead of bootmem

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:   Mon, 19 Sep 2016 15:06:23 +0900 (JST)
From:   Stafford Horne <shorne@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
cc:     Stafford Horne <shorne@...il.com>, jonas@...thpole.se,
        stefan.kristiansson@...nalahti.fi, openrisc@...ts.librecores.org,
        linux-kernel@...r.kernel.org
Subject: Re: openrisc: Consolidate setup to use memblock instead of bootmem



On Sun, 18 Sep 2016, Guenter Roeck wrote:

> On Wed, Apr 06, 2016 at 07:08:41PM +0900, Stafford Horne wrote:
>> Clearing out one todo item. This simplifies the boot process by using
>> the memblock api throughout the init process.
>>
>> The old logic bootstrapped from memblock -> bootmem -> buddy allocator
>> This is now simplified by using NO_BOOTMEM.
>>
>> Signed-off-by: Stafford Horne <shorne@...il.com>
>
> FWIW:
>
> Tested-by: Guenter Roeck <linux@...ck-us.net>

Thank you,

-Stafford