From: kernel test robot <lkp@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-ia64@vger.kernel.org
Subject: [aegl:resctrl2_v65 4/4] fs/resctrl2/arch/x86/amd_mbec.c:189:32: warning: 'bmec_feature' defined but not used
Date: Sat, 9 Sep 2023 06:43:56 +0800 [thread overview]
Message-ID: <202309090610.Z43gD7TB-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git resctrl2_v65
head: 13c888afbee9f7da0a4a969617dea9889da9d711
commit: 13c888afbee9f7da0a4a969617dea9889da9d711 [4/4] resctrl2: AMD Bandwidth Monitoring Event Configuration
config: i386-randconfig-051-20230909 (https://download.01.org/0day-ci/archive/20230909/202309090610.Z43gD7TB-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/20230909/202309090610.Z43gD7TB-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/202309090610.Z43gD7TB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/resctrl2/arch/x86/amd_mbec.c:189:32: warning: 'bmec_feature' defined but not used [-Wunused-const-variable=]
189 | static const struct x86_cpu_id bmec_feature[] = {
| ^~~~~~~~~~~~
vim +/bmec_feature +189 fs/resctrl2/arch/x86/amd_mbec.c
188
> 189 static const struct x86_cpu_id bmec_feature[] = {
190 X86_MATCH_FEATURE(X86_FEATURE_BMEC, 0),
191 { }
192 };
193 MODULE_DEVICE_TABLE(x86cpu, bmec_feature);
194
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-08 22:44 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=202309090610.Z43gD7TB-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).