From: kernel test robot <lkp@intel.com>
To: Alexandre Chartre <alexandre.chartre@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@suse.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: arch/x86/kernel/cpu/bugs.c:776:12: sparse: sparse: symbol 'retbleed_strings' was not declared. Should it be static?
Date: Fri, 15 Jul 2022 06:51:06 +0800 [thread overview]
Message-ID: <202207150647.oLujDthN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: db886979683a8360ced9b24ab1125ad0c4d2cf76
commit: 7fbf47c7ce50b38a64576b150e7011ae73d54669 x86/bugs: Add AMD retbleed= boot parameter
date: 3 weeks ago
config: x86_64-randconfig-s022 (https://download.01.org/0day-ci/archive/20220715/202207150647.oLujDthN-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbf47c7ce50b38a64576b150e7011ae73d54669
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 7fbf47c7ce50b38a64576b150e7011ae73d54669
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kernel/cpu/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/cpu/bugs.c:776:12: sparse: sparse: symbol 'retbleed_strings' was not declared. Should it be static?
vim +/retbleed_strings +776 arch/x86/kernel/cpu/bugs.c
774
775 static enum spectre_v2_mitigation spectre_v2_enabled __ro_after_init =
> 776 SPECTRE_V2_NONE;
777
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-14 22:51 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=202207150647.oLujDthN-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.chartre@oracle.com \
--cc=bp@suse.de \
--cc=jpoimboe@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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