From: kernel test robot <lkp@intel.com>
To: Jagdish Gediya <jvgediya@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Cc: kbuild-all@lists.01.org, baolin.wang@linux.alibaba.com,
dave.hansen@linux.intel.com, ying.huang@intel.com,
aneesh.kumar@linux.ibm.com, shy828301@gmail.com,
weixugc@google.com, gthelen@google.com, dan.j.williams@intel.com,
Jagdish Gediya <jvgediya@linux.ibm.com>
Subject: Re: [PATCH v3 6/7] mm: demotion: expose per-node demotion targets via sysfs
Date: Sat, 23 Apr 2022 16:38:52 +0800 [thread overview]
Message-ID: <202204231602.2DeA4BIa-lkp@intel.com> (raw)
In-Reply-To: <20220422195516.10769-7-jvgediya@linux.ibm.com>
Hi Jagdish,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on linus/master linux/master v5.18-rc3]
[cannot apply to hnaz-mm/master next-20220422]
[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/intel-lab-lkp/linux/commits/Jagdish-Gediya/mm-demotion-Introduce-new-node-state-N_DEMOTION_TARGETS/20220423-035714
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 4e224719f5d9b92abf1e0edfb2a83053208f3026
config: sparc-randconfig-r034-20220422 (https://download.01.org/0day-ci/archive/20220423/202204231602.2DeA4BIa-lkp@intel.com/config)
compiler: sparc64-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/intel-lab-lkp/linux/commit/0717e30f61ac83bd6ec65395bf46fdb5131cb83f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Jagdish-Gediya/mm-demotion-Introduce-new-node-state-N_DEMOTION_TARGETS/20220423-035714
git checkout 0717e30f61ac83bd6ec65395bf46fdb5131cb83f
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross W=1 O=build_dir ARCH=sparc SHELL=/bin/bash drivers/base/
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 >>):
drivers/base/node.c: In function 'demotion_targets_show':
>> drivers/base/node.c:567:39: error: implicit declaration of function 'node_get_demotion_targets' [-Werror=implicit-function-declaration]
567 | nodemask_t demotion_targets = node_get_demotion_targets(dev->id);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/base/node.c:567:39: error: invalid initializer
cc1: some warnings being treated as errors
vim +/node_get_demotion_targets +567 drivers/base/node.c
563
564 static ssize_t demotion_targets_show(struct device *dev,
565 struct device_attribute *attr, char *buf)
566 {
> 567 nodemask_t demotion_targets = node_get_demotion_targets(dev->id);
568
569 return sysfs_emit(buf, "%*pbl\n", nodemask_pr_args(&demotion_targets));
570 }
571 static DEVICE_ATTR_RO(demotion_targets);
572
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-04-23 8:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:55 [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 19:55 ` [PATCH v3 1/7] mm: demotion: Fix demotion targets sharing among sources Jagdish Gediya
2022-04-24 3:25 ` ying.huang
2022-04-25 9:32 ` Jagdish Gediya
2022-04-26 7:26 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 2/7] mm: demotion: Add new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:29 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 3/7] drivers/base/node: Add support to write node_states[] via sysfs Jagdish Gediya
2022-04-22 20:32 ` Wei Xu
2022-04-24 6:25 ` Aneesh Kumar K.V
2022-04-25 9:42 ` Jagdish Gediya
2022-04-24 6:29 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 4/7] device-dax/kmem: Set node state as N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:34 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 5/7] mm: demotion: Build demotion list based on N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:39 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 6/7] mm: demotion: expose per-node demotion targets via sysfs Jagdish Gediya
2022-04-22 20:47 ` Wei Xu
2022-04-23 7:30 ` kernel test robot
2022-04-23 8:38 ` kernel test robot [this message]
2022-04-22 19:55 ` [PATCH v3 7/7] docs: numa: Add documentation for demotion Jagdish Gediya
2022-04-24 3:19 ` [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS ying.huang
2022-04-25 11:15 ` Jagdish Gediya
2022-04-25 13:57 ` Jonathan Cameron
2022-04-25 14:44 ` Aneesh Kumar K V
2022-04-26 10:43 ` Jonathan Cameron
2022-04-27 1:29 ` ying.huang
2022-04-27 2:57 ` Aneesh Kumar K V
2022-04-27 3:34 ` ying.huang
2022-04-25 14:53 ` Aneesh Kumar K V
2022-04-26 10:37 ` Jonathan Cameron
2022-04-26 7:55 ` ying.huang
2022-04-26 9:07 ` Aneesh Kumar K V
2022-04-26 9:10 ` ying.huang
2022-04-26 9:37 ` Jagdish Gediya
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=202204231602.2DeA4BIa-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=jvgediya@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=weixugc@google.com \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).