summaryrefslogtreecommitdiff
path: root/arch/loongarch/include/asm/acpi.h
diff options
context:
space:
mode:
authorHuacai Chen <chenhuacai@loongson.cn>2022-09-02 17:33:42 +0300
committerHuacai Chen <chenhuacai@loongson.cn>2022-09-03 13:01:27 +0300
commite0fba87c854347007fb9fc873e890b686cc61302 (patch)
tree64463acb34f78e5983a5469f351f2720d2a3fd10 /arch/loongarch/include/asm/acpi.h
parentad6846196ab62287e3ba094bb52647132f1998cd (diff)
downloadlinux-e0fba87c854347007fb9fc873e890b686cc61302.tar.xz
LoongArch: Fix section mismatch due to acpi_os_ioremap()
Now acpi_os_ioremap() is marked with __init because it calls memblock_ is_memory() which is also marked with __init in the !ARCH_KEEP_MEMBLOCK case. However, acpi_os_ioremap() is called by ordinary functions such as acpi_os_{read, write}_memory() and causes section mismatch warnings: WARNING: modpost: vmlinux.o: section mismatch in reference: acpi_os_read_memory (section: .text) -> acpi_os_ioremap (section: .init.text) WARNING: modpost: vmlinux.o: section mismatch in reference: acpi_os_write_memory (section: .text) -> acpi_os_ioremap (section: .init.text) Fix these warnings by selecting ARCH_KEEP_MEMBLOCK unconditionally and removing the __init modifier of acpi_os_ioremap(). This can also give a chance to track "memory" and "reserved" memblocks after early boot. Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
Diffstat (limited to 'arch/loongarch/include/asm/acpi.h')
-rw-r--r--arch/loongarch/include/asm/acpi.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/loongarch/include/asm/acpi.h b/arch/loongarch/include/asm/acpi.h
index c5108213876c..17162f494b9b 100644
--- a/arch/loongarch/include/asm/acpi.h
+++ b/arch/loongarch/include/asm/acpi.h
@@ -15,7 +15,7 @@ extern int acpi_pci_disabled;
extern int acpi_noirq;
#define acpi_os_ioremap acpi_os_ioremap
-void __init __iomem *acpi_os_ioremap(acpi_physical_address phys, acpi_size size);
+void __iomem *acpi_os_ioremap(acpi_physical_address phys, acpi_size size);
static inline void disable_acpi(void)
{