From: kernel test robot <lkp@intel.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC] fs: drop_caches: introduce per-node drop_caches interface
Date: Mon, 13 Apr 2026 16:29:27 +0800 [thread overview]
Message-ID: <202604130943.MLP9ZgAQ-lkp@intel.com> (raw)
In-Reply-To: <20260409063503.3475420-1-wangkefeng.wang@huawei.com>
Hi Kefeng,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on brauner-vfs/vfs.all driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus linus/master v7.0-rc7 next-20260410]
[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/Kefeng-Wang/fs-drop_caches-introduce-per-node-drop_caches-interface/20260412-192452
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20260409063503.3475420-1-wangkefeng.wang%40huawei.com
patch subject: [PATCH RFC] fs: drop_caches: introduce per-node drop_caches interface
config: powerpc64-randconfig-002-20260413 (https://download.01.org/0day-ci/archive/20260413/202604130943.MLP9ZgAQ-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260413/202604130943.MLP9ZgAQ-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/202604130943.MLP9ZgAQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/drop_caches.c:148:5: error: redefinition of 'drop_caches_register_node'
148 | int drop_caches_register_node(struct node *node)
| ^
include/linux/fs.h:3661:19: note: previous definition is here
3661 | static inline int drop_caches_register_node(struct node *node) { return 0; }
| ^
>> fs/drop_caches.c:153:6: error: redefinition of 'drop_caches_unregister_node'
153 | void drop_caches_unregister_node(struct node *node)
| ^
include/linux/fs.h:3662:20: note: previous definition is here
3662 | static inline void drop_caches_unregister_node(struct node *node) {}
| ^
2 errors generated.
vim +/drop_caches_register_node +148 fs/drop_caches.c
146
147 static DEVICE_ATTR_WO(drop_caches);
> 148 int drop_caches_register_node(struct node *node)
149 {
150 return device_create_file(&node->dev, &dev_attr_drop_caches);
151 }
152
> 153 void drop_caches_unregister_node(struct node *node)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-04-13 8:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260409063503.3475420-1-wangkefeng.wang@huawei.com>]
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=202604130943.MLP9ZgAQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wangkefeng.wang@huawei.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