From: kernel test robot <lkp@intel.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [weiny2:cxl-cper-2023-12-13 8/9] drivers/firmware/efi/cper_cxl.c:192:1: sparse: sparse: symbol 'cxl_cper_rw_sem' was not declared. Should it be static?
Date: Thu, 14 Dec 2023 22:07:18 +0800 [thread overview]
Message-ID: <202312142211.cbcsaH5v-lkp@intel.com> (raw)
tree: https://github.com/weiny2/linux-kernel.git cxl-cper-2023-12-13
head: effd1d38713375ee60e89f1bef31eea1ba668304
commit: 3394ce85e912b328886077c5a439c65284767bb8 [8/9] firmware/efi: Process CXL Component Events
config: x86_64-randconfig-121-20231214 (https://download.01.org/0day-ci/archive/20231214/202312142211.cbcsaH5v-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231214/202312142211.cbcsaH5v-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/202312142211.cbcsaH5v-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/firmware/efi/cper_cxl.c:192:1: sparse: sparse: symbol 'cxl_cper_rw_sem' was not declared. Should it be static?
drivers/firmware/efi/cper_cxl.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
vim +/cxl_cper_rw_sem +192 drivers/firmware/efi/cper_cxl.c
191
> 192 DECLARE_RWSEM(cxl_cper_rw_sem);
193 static cxl_cper_notifier cper_notifier;
194
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-14 14:07 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=202312142211.cbcsaH5v-lkp@intel.com \
--to=lkp@intel.com \
--cc=ira.weiny@intel.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.