Commit 44c752fe authored by Rahul Lakkireddy's avatar Rahul Lakkireddy Committed by David S. Miller

vmcore: move get_vmcore_size out of __init

Fix below build warning:

WARNING: vmlinux.o(.text+0x422bb8): Section mismatch in reference from
the function vmcore_add_device_dump() to the function
.init.text:get_vmcore_size.constprop.5()

The function vmcore_add_device_dump() references
the function __init get_vmcore_size.constprop.5().
This is often because vmcore_add_device_dump lacks a __init
annotation or the annotation of get_vmcore_size.constprop.5 is wrong.

Fixes: 7efe48df ("vmcore: append device dumps to vmcore as elf notes")
Signed-off-by: default avatarRahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Signed-off-by: default avatarGanesh Goudar <ganeshgr@chelsio.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent a6076fcd
...@@ -649,7 +649,7 @@ static struct vmcore* __init get_new_element(void) ...@@ -649,7 +649,7 @@ static struct vmcore* __init get_new_element(void)
return kzalloc(sizeof(struct vmcore), GFP_KERNEL); return kzalloc(sizeof(struct vmcore), GFP_KERNEL);
} }
static u64 __init get_vmcore_size(size_t elfsz, size_t elfnotesegsz, static u64 get_vmcore_size(size_t elfsz, size_t elfnotesegsz,
struct list_head *vc_list) struct list_head *vc_list)
{ {
u64 size; u64 size;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment