[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190325072022.GD2925@rapoport-lnx>
Date: Mon, 25 Mar 2019 09:20:23 +0200
From: Mike Rapoport <rppt@...ux.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Christoph Hellwig <hch@....de>, Palmer Dabbelt <palmer@...ive.com>,
Richard Kuo <rkuo@...eaurora.org>, linux-arch@...r.kernel.org,
linux-hexagon@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v2 0/4] provide a generic free_initmem implementation
Any comments on this?
On Mon, Feb 18, 2019 at 08:41:21PM +0200, Mike Rapoport wrote:
> Hi,
>
> Many architectures implement free_initmem() in exactly the same or very
> similar way: they wrap the call to free_initmem_default() with sometimes
> different 'poison' parameter.
>
> These patches switch those architectures to use a generic implementation
> that does free_initmem_default(POISON_FREE_INITMEM).
>
> This was inspired by Christoph's patches for free_initrd_mem [1] and I
> shamelessly copied changelog entries from his patches :)
>
> v2: rebased on top of v5.0-rc7 + Christoph's patches for free_initrd_mem
>
> [1] https://lore.kernel.org/lkml/20190213174621.29297-1-hch@lst.de/
>
> Mike Rapoport (4):
> init: provide a generic free_initmem implementation
> hexagon: switch over to generic free_initmem()
> init: free_initmem: poison freed init memory
> riscv: switch over to generic free_initmem()
>
> arch/alpha/mm/init.c | 6 ------
> arch/arc/mm/init.c | 8 --------
> arch/c6x/mm/init.c | 5 -----
> arch/h8300/mm/init.c | 6 ------
> arch/hexagon/mm/init.c | 10 ----------
> arch/microblaze/mm/init.c | 5 -----
> arch/nds32/mm/init.c | 5 -----
> arch/nios2/mm/init.c | 5 -----
> arch/openrisc/mm/init.c | 5 -----
> arch/riscv/mm/init.c | 5 -----
> arch/sh/mm/init.c | 5 -----
> arch/sparc/mm/init_32.c | 5 -----
> arch/unicore32/mm/init.c | 5 -----
> arch/xtensa/mm/init.c | 5 -----
> init/main.c | 5 +++++
> 15 files changed, 5 insertions(+), 80 deletions(-)
>
> --
> 2.7.4
>
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists