From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
Tony Luck <tony.luck@intel.com>
Subject: [intel-tdx:guest-attest-wip 2/3] drivers/virt/coco/tdx-guest/tdx-guest.c:129:32: warning: 'tdx_guest_ids' defined but not used
Date: Wed, 21 Sep 2022 16:45:52 +0800 [thread overview]
Message-ID: <202209211607.tCtTWKbV-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-attest-wip
head: 33cc9e3b6141b4339bceb2591c188d866c7a9052
commit: 3a38d73702055606f2b0a1ea0610767e7142e0cb [2/3] virt: Add TDX guest driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220921/202209211607.tCtTWKbV-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/3a38d73702055606f2b0a1ea0610767e7142e0cb
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-attest-wip
git checkout 3a38d73702055606f2b0a1ea0610767e7142e0cb
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/virt/coco/tdx-guest/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/virt/coco/tdx-guest/tdx-guest.c:129:32: warning: 'tdx_guest_ids' defined but not used [-Wunused-const-variable=]
129 | static const struct x86_cpu_id tdx_guest_ids[] = {
| ^~~~~~~~~~~~~
vim +/tdx_guest_ids +129 drivers/virt/coco/tdx-guest/tdx-guest.c
128
> 129 static const struct x86_cpu_id tdx_guest_ids[] = {
130 X86_MATCH_FEATURE(X86_FEATURE_TDX_GUEST, NULL),
131 {}
132 };
133 MODULE_DEVICE_TABLE(x86cpu, tdx_guest_ids);
134
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-21 8:46 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=202209211607.tCtTWKbV-lkp@intel.com \
--to=lkp@intel.com \
--cc=bagasdotme@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--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
all inboxes | Powered by JetHome®