From: kernel test robot <lkp@intel.com>
To: Ben Horgan <ben.horgan@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
James Morse <james.morse@arm.com>
Subject: [morse:mpam/snapshot/v6.15-rc3 100/110] include/linux/debugfs.h:419:2: warning: void function 'debugfs_create_cpumask' should not return a value
Date: Wed, 30 Apr 2025 02:38:49 +0800 [thread overview]
Message-ID: <202504300247.bnFT3fxj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git mpam/snapshot/v6.15-rc3
head: 2cc3eff27207d40f181a59f04660a1e8e9746ff8
commit: 482d40a25255bb2c3df8cebda0f06cd2af2d4b95 [100/110] debugfs: Add stub to fix the build when debugfs is not enabled
config: arm-randconfig-003-20250430 (https://download.01.org/0day-ci/archive/20250430/202504300247.bnFT3fxj-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504300247.bnFT3fxj-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/202504300247.bnFT3fxj-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from block/blk-sysfs.c:12:
>> include/linux/debugfs.h:419:2: warning: void function 'debugfs_create_cpumask' should not return a value [-Wreturn-mismatch]
419 | return ERR_PTR(-ENODEV);
| ^ ~~~~~~~~~~~~~~~~
1 warning generated.
vim +/debugfs_create_cpumask +419 include/linux/debugfs.h
415
416 static inline void debugfs_create_cpumask(const char *name, umode_t mode,
417 struct dentry *parent, struct cpumask *value)
418 {
> 419 return ERR_PTR(-ENODEV);
420 }
421
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-29 18:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202504300247.bnFT3fxj-lkp@intel.com \
--to=lkp@intel.com \
--cc=ben.horgan@arm.com \
--cc=james.morse@arm.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox