All of lore.kernel.org
 help / color / mirror / Atom feed
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-testing 2/6] drivers/acpi/apei/ghes.c:710:1: sparse: sparse: symbol 'cxl_cper_fifo' was not declared. Should it be static?
Date: Wed, 24 Apr 2024 00:47:04 +0800	[thread overview]
Message-ID: <202404240040.YT2KAtSx-lkp@intel.com> (raw)

tree:   https://github.com/weiny2/linux-kernel.git cxl-cper-testing
head:   9b1f33314e8488506dbad63dc1c896386d4803d6
commit: 5cda2b55e5656f16f327e45c71af123d9d934fdb [2/6] acpi/ghes: Process CXL Component Events
config: i386-randconfig-063-20240423 (https://download.01.org/0day-ci/archive/20240424/202404240040.YT2KAtSx-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240424/202404240040.YT2KAtSx-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/202404240040.YT2KAtSx-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/acpi/apei/ghes.c:710:1: sparse: sparse: symbol 'cxl_cper_fifo' was not declared. Should it be static?
>> drivers/acpi/apei/ghes.c:721:20: sparse: sparse: symbol 'cxl_cper_work' was not declared. Should it be static?
   drivers/acpi/apei/ghes.c:723:13: sparse: sparse: context imbalance in 'cxl_cper_post_event' - different lock contexts for basic block
   drivers/acpi/apei/ghes.c:756:5: sparse: sparse: context imbalance in 'cxl_cper_register_callback' - different lock contexts for basic block

vim +/cxl_cper_fifo +710 drivers/acpi/apei/ghes.c

   709	
 > 710	DEFINE_KFIFO(cxl_cper_fifo, struct cxl_cper_work_data, 32);
   711	static DEFINE_SPINLOCK(cxl_cper_work_lock);
   712	static cxl_cper_callback cper_callback;
   713	static void cxl_cper_cb_fn(struct work_struct *work)
   714	{
   715		struct cxl_cper_work_data wd;
   716	
   717		while (kfifo_get(&cxl_cper_fifo, &wd))
   718			cper_callback(wd.event_type, &wd.rec);
   719	}
   720	static DECLARE_WORK(cxl_cb_work, cxl_cper_cb_fn);
 > 721	struct work_struct *cxl_cper_work = NULL;
   722	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-04-23 16:47 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=202404240040.YT2KAtSx-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.