tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master head: f2fb1afc57304f9dd68c20a08270e287470af2eb commit: e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c [14484/14891] MIPS: replace add_memory_region with memblock config: mips-decstation_r4k_defconfig (attached as .config) compiler: mipsel-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commi... git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git git fetch --no-tags linux-next master git checkout e7ae8d174eec0b3b9de92b76abc15f3f53b98f1c # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp(a)intel.com&gt; All warnings (new ones prefixed by >>, old ones prefixed by <<): << WARNING: modpost: vmlinux.o(.text.unlikely+0x2834): Section mismatch in reference from the function pmax_setup_memory_region() to the function .init.text:add_memory_region() The function pmax_setup_memory_region() references the function __meminit memblock_add(). This is often because pmax_setup_memory_region lacks a __meminit annotation or the annotation of memblock_add is wrong. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org