From: kernel test robot <lkp@intel.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
akpm@linux-foundation.org, ying.huang@intel.com,
dave.hansen@linux.intel.com
Cc: kbuild-all@lists.01.org, ziy@nvidia.com, osalvador@suse.de,
shy828301@gmail.com, baolin.wang@linux.alibaba.com,
zhongjiang-ali@linux.alibaba.com, xlpang@linux.alibaba.com,
linux-mm@kvack.org
Subject: Re: [PATCH v2 2/2] mm: migrate: Allocate the node_demotion structure dynamically
Date: Thu, 11 Nov 2021 21:42:26 +0800 [thread overview]
Message-ID: <202111112144.S9JLplY7-lkp@intel.com> (raw)
In-Reply-To: <e39502af91e12ba1a4bef3be4d05b11b2c7a7a9f.1636616548.git.baolin.wang@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Hi Baolin,
I love your patch! Yet something to improve:
[auto build test ERROR on hnaz-mm/master]
[also build test ERROR on v5.15 next-20211111]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Baolin-Wang/Support-multiple-target-nodes-demotion/20211111-154935
base: https://github.com/hnaz/linux-mm master
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 11.2.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://github.com/0day-ci/linux/commit/fda28dda2298e1ef984376940071c8435e9b1399
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Baolin-Wang/Support-multiple-target-nodes-demotion/20211111-154935
git checkout fda28dda2298e1ef984376940071c8435e9b1399
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> mm/migrate.c:1159:23: error: 'target_nodes_max' defined but not used [-Werror=unused-variable]
1159 | static unsigned short target_nodes_max;
| ^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/target_nodes_max +1159 mm/migrate.c
1157
1158 static struct demotion_nodes *node_demotion[MAX_NUMNODES] __read_mostly;
> 1159 static unsigned short target_nodes_max;
1160
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62414 bytes --]
prev parent reply other threads:[~2021-11-11 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 7:48 [PATCH v2 0/2] Support multiple target nodes demotion Baolin Wang
2021-11-11 7:48 ` [PATCH v2 1/2] mm: migrate: " Baolin Wang
2021-11-11 8:20 ` Huang, Ying
2021-11-11 10:52 ` Baolin Wang
2021-11-11 7:48 ` [PATCH v2 2/2] mm: migrate: Allocate the node_demotion structure dynamically Baolin Wang
2021-11-11 8:51 ` Huang, Ying
2021-11-11 11:20 ` Baolin Wang
2021-11-11 23:39 ` Huang, Ying
2021-11-11 13:42 ` kernel test robot [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=202111112144.S9JLplY7-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=xlpang@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zhongjiang-ali@linux.alibaba.com \
--cc=ziy@nvidia.com \
/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