diff options
| author | Mike Rapoport <rppt@linux.ibm.com> | 2019-04-26 10:26:29 +1000 |
|---|---|---|
| committer | Stephen Rothwell <sfr@canb.auug.org.au> | 2019-04-28 01:04:07 +1000 |
| commit | 498f029b010ca31c8fee944ecbb7b985eb4546ca (patch) | |
| tree | a42ee6d73fb8e0c11710ebc6b59ad26cc075c151 /arch/h8300/mm | |
| parent | 44806b25b2846b46a904bc58ffac40abcab5f559 (diff) | |
| download | linux-next-498f029b010ca31c8fee944ecbb7b985eb4546ca.tar.gz | |
init: provide a generic free_initmem implementation
Patch series "provide a generic free_initmem implementation", v2.
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 :)
[1] https://lore.kernel.org/lkml/20190213174621.29297-1-hch@lst.de/
This patch (of 2):
For most architectures free_initmem just a wrapper for the same
free_initmem_default(-1) call. Provide that as a generic implementation
marked __weak.
Link: http://lkml.kernel.org/r/1550515285-17446-2-git-send-email-rppt@linux.ibm.com
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Palmer Dabbelt <palmer@sifive.com>
Cc: Richard Kuo <rkuo@codeaurora.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Diffstat (limited to 'arch/h8300/mm')
| -rw-r--r-- | arch/h8300/mm/init.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/arch/h8300/mm/init.c b/arch/h8300/mm/init.c index ea635c9025fe..1eab16b1a0bc 100644 --- a/arch/h8300/mm/init.c +++ b/arch/h8300/mm/init.c @@ -102,9 +102,3 @@ void __init mem_init(void) mem_init_print_info(NULL); } - -void -free_initmem(void) -{ - free_initmem_default(-1); -} |