All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry.memverge@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v4 1/3] mm/memcontrol: implement memcg.interleave_weights
Date: Thu, 9 Nov 2023 16:38:37 +0800	[thread overview]
Message-ID: <202311091652.AOSQhXGV-lkp@intel.com> (raw)
In-Reply-To: <20231109002517.106829-2-gregory.price@memverge.com>

Hi Gregory,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on cxl/next]
[also build test ERROR on tj-cgroup/for-next cxl/pending v6.6]
[cannot apply to akpm-mm/mm-everything linus/master next-20231109]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Gregory-Price/mm-mempolicy-implement-weighted-interleave/20231109-092543
base:   https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git next
patch link:    https://lore.kernel.org/r/20231109002517.106829-2-gregory.price%40memverge.com
patch subject: [RFC PATCH v4 1/3] mm/memcontrol: implement memcg.interleave_weights
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20231109/202311091652.AOSQhXGV-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231109/202311091652.AOSQhXGV-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/202311091652.AOSQhXGV-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/alpha/mm/init.c:261:1: warning: no previous prototype for 'srm_paging_stop' [-Wmissing-prototypes]
     261 | srm_paging_stop (void)
         | ^~~~~~~~~~~~~~~
   In file included from include/linux/swap.h:9,
                    from arch/alpha/mm/init.c:20:
>> include/linux/memcontrol.h:1620:21: error: 'mem_cgroup_get_il_weights' defined but not used [-Werror=unused-function]
    1620 | static unsigned int mem_cgroup_get_il_weights(nodemask_t *nodes,
         |                     ^~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/memcontrol.h:1618:22: error: 'mem_cgroup_get_il_weight' defined but not used [-Werror=unused-function]
    1618 | static unsigned char mem_cgroup_get_il_weight(unsigned int nid) { return 0; }
         |                      ^~~~~~~~~~~~~~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +/mem_cgroup_get_il_weights +1620 include/linux/memcontrol.h

  1617	
> 1618	static unsigned char mem_cgroup_get_il_weight(unsigned int nid) { return 0; }
  1619	
> 1620	static unsigned int mem_cgroup_get_il_weights(nodemask_t *nodes,
  1621						      unsigned char *weights)
  1622	{
  1623		return 0;
  1624	}
  1625	#endif /* CONFIG_MEMCG */
  1626	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-11-09  8:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <klhcqksrg7uvdrf6hoi5tegifycjltz2kx2d62hapmw3ulr7oa@woibsnrpgox4>
2023-11-09  0:25 ` [RFC PATCH v4 0/3] memcg weighted interleave mempolicy control Gregory Price
2023-11-09  0:25   ` [RFC PATCH v4 1/3] mm/memcontrol: implement memcg.interleave_weights Gregory Price
2023-11-09  8:38     ` kernel test robot [this message]
2023-11-09  0:25   ` [RFC PATCH v4 2/3] mm/mempolicy: implement weighted interleave Gregory Price
2023-11-09 13:36     ` kernel test robot
2023-11-10 15:26     ` Ravi Jonnalagadda
2023-11-09  0:25   ` [RFC PATCH v4 3/3] Documentation: sysfs entries for cgroup.memory.interleave_weights Gregory Price
2023-11-09 10:02   ` [RFC PATCH v4 0/3] memcg weighted interleave mempolicy control Michal Hocko
2023-11-09 15:10     ` Gregory Price
2023-11-09 16:34     ` Gregory Price
2023-11-10  9:05       ` Michal Hocko
2023-11-10 21:24         ` Gregory Price
2023-11-09 22:48   ` John Groves
2023-11-10 22:05     ` tj
2023-11-10 22:29       ` Gregory Price
2023-11-11  3:05         ` tj
2023-11-11  3:42           ` Gregory Price
2023-11-11 11:16             ` tj
2023-11-11 23:54               ` Dan Williams
2023-11-13  2:22                 ` Gregory Price
2023-11-14  9:43             ` Michal Hocko
2023-11-14 15:50               ` Gregory Price
2023-11-14 17:01                 ` Michal Hocko
2023-11-14 17:49                   ` Gregory Price
2023-11-15  5:56                     ` Huang, Ying
2023-12-04  3:33                       ` Gregory Price
2023-12-04  8:19                         ` Huang, Ying
2023-12-04 13:50                           ` Gregory Price
2023-12-05  9:01                             ` Huang, Ying
2023-12-05 14:47                               ` Gregory Price
2023-12-06  0:50                                 ` Huang, Ying
2023-12-06  2:01                                   ` Gregory Price
2023-11-10  6:16   ` Huang, Ying
2023-11-10 19:54     ` Gregory Price
2023-11-13  1:31       ` Huang, Ying
2023-11-13  2:28         ` Gregory Price

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=202311091652.AOSQhXGV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gourry.memverge@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.