Hi lijiang, Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master] [cannot apply to v5.4-rc4 next-20191024] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/lijiang/x86-kdump-always-reserve-the-low-1MiB-when-the-crashkernel/20191025-030439 base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git f116b96685a046a89c25d4a6ba2da489145c8888 config: i386-defconfig (attached as .config) compiler: gcc-7 (Debian 7.4.0-14) 7.4.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 If you fix the issue, kindly add following tag Reported-by: kbuild test robot <[email protected]> All warnings (new ones prefixed by >>): >> WARNING: vmlinux.o(.text+0xe39b7): Section mismatch in reference from the >> function kexec_reserve_low_1MiB() to the variable >> .init.data:boot_command_line The function kexec_reserve_low_1MiB() references the variable __initdata boot_command_line. This is often because kexec_reserve_low_1MiB lacks a __initdata annotation or the annotation of boot_command_line is wrong. -- >> WARNING: vmlinux.o(.text+0xe39d0): Section mismatch in reference from the >> function kexec_reserve_low_1MiB() to the function >> .meminit.text:memblock_reserve() The function kexec_reserve_low_1MiB() references the function __meminit memblock_reserve(). This is often because kexec_reserve_low_1MiB lacks a __meminit annotation or the annotation of memblock_reserve is wrong. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
.config.gz
Description: application/gzip
_______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
