Hi, [auto build test WARNING on arm64/for-next/core] [also build test WARNING on v4.7-rc4 next-20160623] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Dennis-Chen/mm-memblock-Add-some-new-functions-to-address-the-mem-limit-issue/20160623-193344 base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux for-next/core config: x86_64-randconfig-s0-06232144 (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All warnings (new ones prefixed by >>): >> WARNING: vmlinux.o(.text.unlikely+0x330c): Section mismatch in reference from the function __find_max_addr() to the variable .meminit.data:memblock The function __find_max_addr() references the variable __meminitdata memblock. This is often because __find_max_addr lacks a __meminitdata annotation or the annotation of memblock is wrong. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
Attachment:
.config.gz
Description: Binary data
