Paul Mackerras <paulus@xxxxxxxxxx> writes: > On Tue, Nov 22, 2016 at 10:00:58PM +1100, Michael Ellerman wrote: >> kbuild test robot <lkp@xxxxxxxxx> writes: >> > [auto build test WARNING on powerpc/next] >> > [cannot apply to v4.9-rc6 next-20161117] >> > [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/Paul-Mackerras/powerpc-64-Preparation-for-KVM-support-on-POWER9/20161121-133431 >> > base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next >> > config: powerpc-allyesconfig (attached as .config) >> > compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 >> > reproduce: >> > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross >> > chmod +x ~/bin/make.cross >> > # save the attached .config to linux build tree >> > make.cross ARCH=powerpc >> > >> > All warnings (new ones prefixed by >>): >> > >> >>> WARNING: vmlinux.o(.text+0x5c650): Section mismatch in reference from the function .mmu_partition_table_init() to the function .init.text:.memblock_alloc_base() >> > The function .mmu_partition_table_init() references >> > the function __init .memblock_alloc_base(). >> >> > This is often because .mmu_partition_table_init lacks a __init >> >> Indeed that looks like the problem. >> >> Paul have you already merged the topic branch, or can I squash in a fix >> for this? Or I'll just do it on top. > > I haven't pushed out the merge, so go ahead. OK done. I also pulled in Mikey's HFSCR patch. New HEAD is 02ed21aeda0e ("powerpc/powernv: Define and set POWER9 HFSCR doorbell bit"). cheers -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
