From: kernel test robot <lkp@intel.com>
To: Tedd Ho-Jeong An <tedd.an@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Kiran K <kiran.k@intel.com>
Subject: [linux-next:master 11453/12321] drivers/bluetooth/btintel_pcie.c:607:33: sparse: sparse: symbol 'causes_list' was not declared. Should it be static?
Date: Fri, 10 May 2024 06:59:22 +0800 [thread overview]
Message-ID: <202405100654.0djvoryZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 704ba27ac55579704ba1289392448b0c66b56258
commit: 0636fdbb117aad116d33b04dc38f346ba243e1a2 [11453/12321] Bluetooth: btintel_pcie: Add support for PCIe transport
config: powerpc64-randconfig-r133-20240510 (https://download.01.org/0day-ci/archive/20240510/202405100654.0djvoryZ-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240510/202405100654.0djvoryZ-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/202405100654.0djvoryZ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/bluetooth/btintel_pcie.c:607:33: sparse: sparse: symbol 'causes_list' was not declared. Should it be static?
vim +/causes_list +607 drivers/bluetooth/btintel_pcie.c
606
> 607 struct btintel_pcie_causes_list causes_list[] = {
608 { BTINTEL_PCIE_MSIX_FH_INT_CAUSES_0, BTINTEL_PCIE_CSR_MSIX_FH_INT_MASK, 0x00 },
609 { BTINTEL_PCIE_MSIX_FH_INT_CAUSES_1, BTINTEL_PCIE_CSR_MSIX_FH_INT_MASK, 0x01 },
610 { BTINTEL_PCIE_MSIX_HW_INT_CAUSES_GP0, BTINTEL_PCIE_CSR_MSIX_HW_INT_MASK, 0x20 },
611 };
612
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-09 22:59 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=202405100654.0djvoryZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-mm@kvack.org \
--cc=luiz.von.dentz@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tedd.an@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).