From: Philip Li <philip.li@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 10448/11214] arch/microblaze/include/asm/cacheflush.h:77:13: warning: 'flush_dcache_folio' defined but not used
Date: Tue, 22 Aug 2023 09:55:08 +0800 [thread overview]
Message-ID: <ZOQVfFhvdB61CuO2@rli9-mobl> (raw)
In-Reply-To: <ZOOqPZNvScEc+3aK@casper.infradead.org>
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@intel.com/config)
> > compiler: microblaze-linux-gcc (GCC) 12.3.0
> > reproduce: (https://download.01.org/0day-ci/archive/20230822/202308220106.VDWkCsdG-lkp@intel.com/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@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202308220106.VDWkCsdG-lkp@intel.com/
> >
> > 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.
>
prev parent reply other threads:[~2023-08-22 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 17:21 kernel test robot
2023-08-21 18:17 ` Matthew Wilcox
2023-08-22 1:55 ` Philip Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOQVfFhvdB61CuO2@rli9-mobl \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox