From: kernel test robot <lkp@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [vishal:vv/dax_abi 2/5] drivers/dax/bus.c:19:1: sparse: sparse: symbol 'dax_region_rwsem' was not declared. Should it be static?
Date: Fri, 19 Jan 2024 00:12:08 +0800 [thread overview]
Message-ID: <202401190002.akeSPLMC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vishal/linux.git vv/dax_abi
head: d3de88ca301b687923a19a41d16a22afcd9c40a1
commit: 2e7ab04d7b9be08918c4166412b02550d545819c [2/5] dax/bus.c: replace driver-core lock usage by a local rwsem
config: x86_64-randconfig-121-20240118 (https://download.01.org/0day-ci/archive/20240119/202401190002.akeSPLMC-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240119/202401190002.akeSPLMC-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/202401190002.akeSPLMC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/dax/bus.c:19:1: sparse: sparse: symbol 'dax_region_rwsem' was not declared. Should it be static?
>> drivers/dax/bus.c:25:1: sparse: sparse: symbol 'dax_dev_rwsem' was not declared. Should it be static?
vim +/dax_region_rwsem +19 drivers/dax/bus.c
14
15 /*
16 * All changes to the dax region configuration occur with this lock held
17 * for write.
18 */
> 19 DECLARE_RWSEM(dax_region_rwsem);
20
21 /*
22 * All changes to the dax device configuration occur with this lock held
23 * for write.
24 */
> 25 DECLARE_RWSEM(dax_dev_rwsem);
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-18 16:12 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=202401190002.akeSPLMC-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vishal.l.verma@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.