From: Mel Gorman <mgorman@suse.de>
To: kbuild-all@lists.01.org
Subject: Re: [mel:mm-percpu-local_lock-v1r10 11/16] mm/vmstat.c:1690:28: warning: variable 'pzstats' set but not used
Date: Wed, 24 Mar 2021 09:36:22 +0000 [thread overview]
Message-ID: <20210324093622.GM15768@suse.de> (raw)
In-Reply-To: <202103231710.D371sKJP-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On Tue, Mar 23, 2021 at 05:31:15PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git mm-percpu-local_lock-v1r10
> head: e1091ede0db3313db25301e58af64ca32864c27d
> commit: 6908776bbd1821e6b83b107cd2d8d8339a3c1a31 [11/16] mm/page_alloc: Split per cpu page lists and zone stats
> config: m68k-randconfig-r011-20210322 (attached as .config)
> compiler: m68k-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
> # https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git/commit/?id=6908776bbd1821e6b83b107cd2d8d8339a3c1a31
> git remote add mel https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> git fetch --no-tags mel mm-percpu-local_lock-v1r10
> git checkout 6908776bbd1821e6b83b107cd2d8d8339a3c1a31
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
Thanks. As this will not be a separate patch to fix the problem, I added
this to the Certificate of Origin chain. I assume this is acceptable.
[lkp(a)intel.com: Check struct per_cpu_zonestat has a non-zero size]
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2021-03-24 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 9:31 [mel:mm-percpu-local_lock-v1r10 11/16] mm/vmstat.c:1690:28: warning: variable 'pzstats' set but not used kernel test robot
2021-03-24 9:36 ` Mel Gorman [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=20210324093622.GM15768@suse.de \
--to=mgorman@suse.de \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.