From: Mike Rapoport <rppt@linux.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Palmer Dabbelt <palmer@sifive.com>,
Richard Kuo <rkuo@codeaurora.org>,
linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH v2 0/4] provide a generic free_initmem implementation
Date: Mon, 18 Feb 2019 20:41:21 +0200 [thread overview]
Message-ID: <1550515285-17446-1-git-send-email-rppt@linux.ibm.com> (raw)
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
next reply other threads:[~2019-02-18 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 18:41 Mike Rapoport [this message]
2019-02-18 18:41 ` [PATCH v2 1/4] init: provide a generic free_initmem implementation Mike Rapoport
2019-02-18 18:41 ` [PATCH v2 2/4] hexagon: switch over to generic free_initmem() Mike Rapoport
2019-02-18 18:41 ` [PATCH v2 3/4] init: free_initmem: poison freed init memory Mike Rapoport
2019-02-18 18:41 ` [PATCH v2 4/4] riscv: switch over to generic free_initmem() Mike Rapoport
2019-03-25 7:20 ` [PATCH v2 0/4] provide a generic free_initmem implementation Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1550515285-17446-1-git-send-email-rppt@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=rkuo@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).