aboutsummaryrefslogtreecommitdiff
path: root/arch/openrisc/mm/init.c
diff options
context:
space:
mode:
authorMike Rapoport <[email protected]>2019-05-13 17:18:40 -0700
committerLinus Torvalds <[email protected]>2019-05-14 09:47:47 -0700
commit997aef68af3ef1f2cb97da1c0b41a5afa87f63e2 (patch)
tree3abeb4f6d3dd24b804cbf1474fe606fc8c67a537 /arch/openrisc/mm/init.c
parentf94f7434cbbb02f7eb55ed5ad66284023c47968f (diff)
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/[email protected]/ 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/[email protected] Signed-off-by: Mike Rapoport <[email protected]> Reviewed-by: Andrew Morton <[email protected]> Cc: Christoph Hellwig <[email protected]> Cc: Palmer Dabbelt <[email protected]> Cc: Richard Kuo <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'arch/openrisc/mm/init.c')
-rw-r--r--arch/openrisc/mm/init.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/arch/openrisc/mm/init.c b/arch/openrisc/mm/init.c
index 08df7f0b1d96..abe87e54e231 100644
--- a/arch/openrisc/mm/init.c
+++ b/arch/openrisc/mm/init.c
@@ -223,8 +223,3 @@ void __init mem_init(void)
mem_init_done = 1;
return;
}
-
-void free_initmem(void)
-{
- free_initmem_default(-1);
-}