On Mon, Aug 21, 2023 at 07:17:33PM +0100, Matthew Wilcox wrote: > On Tue, Aug 22, 2023 at 01:21:43AM +0800, kernel test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > > head: 47d9bb711707d15b19fad18c8e2b4b027a264a3a > > commit: 2fcc20defd8a07415f6b346d941c22c50bbdada5 [10448/11214] microblaze: implement the new page table range API > > config: microblaze-allnoconfig (https://download.01.org/0day-ci/archive/20230822/202308220106.VDWkCsdG-lkp@xxxxxxxxx/config) > > compiler: microblaze-linux-gcc (GCC) 12.3.0 > > reproduce: (https://download.01.org/0day-ci/archive/20230822/202308220106.VDWkCsdG-lkp@xxxxxxxxx/reproduce) > > > > If you fix the issue in a separate patch/commit (i.e. not just a new version of > > the same patch/commit), kindly add following tags > > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202308220106.VDWkCsdG-lkp@xxxxxxxxx/ > > > > All warnings (new ones prefixed by >>): > > > > In file included from kernel/signal.c:57: > > >> arch/microblaze/include/asm/cacheflush.h:77:13: warning: 'flush_dcache_folio' defined but not used [-Wunused-function] > > 77 | static void flush_dcache_folio(struct folio *folio) > > The bug is real, but I'm a little concerned that I got an email from > the testbot a few weeks ago suggesting: > > microblaze randconfig-r002-20230731 gcc > microblaze randconfig-r011-20230731 gcc > microblaze randconfig-r014-20230731 gcc > > all passed. Perhaps you could do allnoconfig testing more frequently? > Those tests should be quick to run since they are allnoconfig ... Got it, we will better balance the test resources to build test the basic configs like allnoconfig in early time, and to include the results in build summary mail. Sorry for the "false safe" summary report for this commit. >
