On Tue, 24 Jul 2018, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: 3946cd385042069ec57d3f04240def53b4eed7e5 > commit: 5d2f33872046e7ffdd62dd80472cd466ea8407ac [7986/8610] mm, vmacache: hash addresses based on pmd > config: microblaze-nommu_defconfig (attached as .config) > compiler: microblaze-linux-gcc (GCC) 8.1.0 > reproduce: > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > git checkout 5d2f33872046e7ffdd62dd80472cd466ea8407ac > # save the attached .config to linux build tree > GCC_VERSION=8.1.0 make.cross ARCH=microblaze > > Note: the linux-next/master HEAD 3946cd385042069ec57d3f04240def53b4eed7e5 builds fine. > It may have been fixed somewhere. > Yes, this Note is accurate, nommu_defconfig on microblaze works fine at HEAD due to commit 63a0a84adc08 ("mm, vmacache: hash addresses based on pmd fix"). I'm not sure this should have sent an email, tbh.
