[kbuild-all] [rppt:memblock/iterators-cleanup/v3 16/17] WARNING: modpost: vmlinux.o(.text+0xc): Section mismatch in reference from the function nexthop_find_by_id() to the variable .meminit.data:memblock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git memblock/iterators-cleanup/v3 head: f0d593460d044672ca2ea065efc283e30dd23ef1 commit: 0aceec0b635f55f8968ec5e42fe4e66b6a55e71d [16/17] memblock: implement for_each_reserved_mem_region() using __next_mem_region() config: parisc-randconfig-c003-20200810 (attached as .config) compiler: hppa-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 git checkout 0aceec0b635f55f8968ec5e42fe4e66b6a55e71d # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc 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 <<): The function nexthop_find_by_id() references the variable __meminitdata memblock. This is often because nexthop_find_by_id lacks a __meminitdata annotation or the annotation of memblock is wrong. -- The function __mincore_unmapped_range() references the variable __meminitdata memblock. This is often because __mincore_unmapped_range lacks a __meminitdata annotation or the annotation of memblock is wrong. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org