From: kernel test robot <lkp@intel.com>
To: Muchun Song <songmuchun@bytedance.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
mike.kravetz@oracle.com, akpm@linux-foundation.org,
osalvador@suse.de, david@redhat.com, ying.huang@intel.com,
aneesh.kumar@linux.ibm.com, rientjes@google.com
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: hugetlb: eliminate memory-less nodes handling
Date: Fri, 2 Sep 2022 12:48:26 +0800 [thread overview]
Message-ID: <202209021255.1ChhyCsl-lkp@intel.com> (raw)
In-Reply-To: <20220901083023.42319-1-songmuchun@bytedance.com>
Hi Muchun,
I love your patch! Yet something to improve:
[auto build test ERROR on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Muchun-Song/mm-hugetlb-eliminate-memory-less-nodes-handling/20220901-163132
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
config: loongarch-buildonly-randconfig-r004-20220901 (https://download.01.org/0day-ci/archive/20220902/202209021255.1ChhyCsl-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.1.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/8e3d203cb06be81565d117b3f6d5e279a833174c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Muchun-Song/mm-hugetlb-eliminate-memory-less-nodes-handling/20220901-163132
git checkout 8e3d203cb06be81565d117b3f6d5e279a833174c
# save the config file
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 ARCH=loongarch
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/base/node.c: In function 'register_node':
>> drivers/base/node.c:614:17: error: implicit declaration of function 'hugetlb_register_node'; did you mean 'unregister_node'? [-Werror=implicit-function-declaration]
614 | hugetlb_register_node(node);
| ^~~~~~~~~~~~~~~~~~~~~
| unregister_node
drivers/base/node.c: In function 'unregister_node':
>> drivers/base/node.c:630:9: error: implicit declaration of function 'hugetlb_unregister_node'; did you mean 'unregister_node'? [-Werror=implicit-function-declaration]
630 | hugetlb_unregister_node(node);
| ^~~~~~~~~~~~~~~~~~~~~~~
| unregister_node
cc1: some warnings being treated as errors
vim +614 drivers/base/node.c
594
595 /*
596 * register_node - Setup a sysfs device for a node.
597 * @num - Node number to use when creating the device.
598 *
599 * Initialize and register the node device.
600 */
601 static int register_node(struct node *node, int num)
602 {
603 int error;
604
605 node->dev.id = num;
606 node->dev.bus = &node_subsys;
607 node->dev.release = node_device_release;
608 node->dev.groups = node_dev_groups;
609 error = device_register(&node->dev);
610
611 if (error) {
612 put_device(&node->dev);
613 } else {
> 614 hugetlb_register_node(node);
615 compaction_register_node(node);
616 }
617
618 return error;
619 }
620
621 /**
622 * unregister_node - unregister a node device
623 * @node: node going away
624 *
625 * Unregisters a node device @node. All the devices on the node must be
626 * unregistered before calling this function.
627 */
628 void unregister_node(struct node *node)
629 {
> 630 hugetlb_unregister_node(node);
631 compaction_unregister_node(node);
632 node_remove_accesses(node);
633 node_remove_caches(node);
634 device_unregister(&node->dev);
635 }
636
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-02 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:30 [PATCH] mm: hugetlb: eliminate memory-less nodes handling Muchun Song
2022-09-01 8:50 ` David Hildenbrand
2022-09-02 2:39 ` Muchun Song
2022-09-01 9:00 ` Aneesh Kumar K V
2022-09-01 9:03 ` David Hildenbrand
2022-09-02 3:42 ` Muchun Song
2022-09-02 4:48 ` 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=202209021255.1ChhyCsl-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=songmuchun@bytedance.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 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.