linux-kernel - Re: [PATCH v3 0/3] MIPS: Fix some issues about arch_mem

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] [day] [month] [year] [list]

Message-ID: <20200421150624.GA16684@alpha.franken.de>
Date:   Tue, 21 Apr 2020 17:06:24 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Tiezhu Yang <yangtiezhu@...ngson.cn>
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        Xuefeng Li <lixuefeng@...ngson.cn>
Subject: Re: [PATCH v3 0/3] MIPS: Fix some issues about arch_mem_init()

On Tue, Apr 21, 2020 at 07:59:43PM +0800, Tiezhu Yang wrote:
> v3:
>   - remove the Fixes tag of patch 2/3
> 
> v2:
>   - modify the subject of patch 3/3
> 
> Tiezhu Yang (3):
>   MIPS: Do not initialise globals to 0
>   MIPS: Cleanup code about plat_mem_setup()
>   MIPS: Make sparse_init() using top-down allocation
> 
>  arch/mips/include/asm/bootinfo.h |  2 +-
>  arch/mips/kernel/setup.c         | 14 +++++++++++---
>  2 files changed, 12 insertions(+), 4 deletions(-)

all three patches applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]