All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Borislav Petkov <bp@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: arch/x86/kernel/irq_64.c:26:1: sparse: sparse: symbol '__pcpu_scope_irq_stack_backing_store' was not declared. Should it be static?
Date: Mon, 25 Dec 2023 02:12:16 +0800	[thread overview]
Message-ID: <202312250248.UgnvTAFE-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   861deac3b092f37b2c5e6871732f3e11486f7082
commit: e6401c13093173aad709a5c6de00cf8d692ee786 x86/irq/64: Split the IRQ stack into its own pages
date:   4 years, 8 months ago
config: x86_64-randconfig-122-20231101 (https://download.01.org/0day-ci/archive/20231225/202312250248.UgnvTAFE-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231225/202312250248.UgnvTAFE-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/202312250248.UgnvTAFE-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/irq_64.c:26:1: sparse: sparse: symbol '__pcpu_scope_irq_stack_backing_store' was not declared. Should it be static?

vim +/__pcpu_scope_irq_stack_backing_store +26 arch/x86/kernel/irq_64.c

    25	
  > 26	DEFINE_PER_CPU_PAGE_ALIGNED(struct irq_stack, irq_stack_backing_store) __visible;
    27	DECLARE_INIT_PER_CPU(irq_stack_backing_store);
    28	

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

                 reply	other threads:[~2023-12-24 18:13 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=202312250248.UgnvTAFE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    /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.