From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Andi Kleen <ak@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: [intel-tdx:guest-filter 6/33] arch/x86/coco/tdx/filter.c:25:22: sparse: sparse: symbol 'pci_allow_ids' was not declared. Should it be static?
Date: Sat, 13 May 2023 04:40:11 +0800 [thread overview]
Message-ID: <202305130452.FZzb5bhB-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-filter
head: b143cfba688689945ae56d38a6f76100859b5025
commit: ad3392a755b5c4440bc92da2a95e8ec04caf0d6a [6/33] x86/tdx: Add device filter support for x86 TDX guest platform
config: x86_64-randconfig-s021 (https://download.01.org/0day-ci/archive/20230513/202305130452.FZzb5bhB-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel/tdx/commit/ad3392a755b5c4440bc92da2a95e8ec04caf0d6a
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-filter
git checkout ad3392a755b5c4440bc92da2a95e8ec04caf0d6a
# 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 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/coco/tdx/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305130452.FZzb5bhB-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/coco/tdx/filter.c:25:22: sparse: sparse: symbol 'pci_allow_ids' was not declared. Should it be static?
vim +/pci_allow_ids +25 arch/x86/coco/tdx/filter.c
16
17 /*
18 * Allow list for PCI bus
19 *
20 * NOTE: Device ID is duplicated here. But for small list
21 * of devices, it is easier to maintain the duplicated list
22 * here verses exporting the device ID table from the driver
23 * and use it.
24 */
> 25 struct pci_device_id pci_allow_ids[] = {
26 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO_TRANS_ID_NET) },
27 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO_TRANS_ID_BLOCK) },
28 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO_TRANS_ID_CONSOLE) },
29 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO_TRANS_ID_9P) },
30 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO1_ID_NET) },
31 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO1_ID_BLOCK) },
32 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO1_ID_CONSOLE) },
33 { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, VIRTIO1_ID_9P) },
34 { 0, },
35 };
36
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-05-12 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 20:40 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 1:02 [intel-tdx:guest-filter 6/33] arch/x86/coco/tdx/filter.c:25:22: sparse: sparse: symbol 'pci_allow_ids' was not declared. Should it be static? kernel test robot
2023-01-03 0:17 kernel test robot
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=202305130452.FZzb5bhB-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.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 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.