From: kernel test robot <lkp@intel.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, vigneshr@ti.com, nm@ti.com,
Achal Verma <a-verma1@ti.com>
Subject: [ti:ti-linux-6.1.y-wip 4/64] drivers/pci/controller/dwc/pci-keystone.c:292:6: sparse: sparse: symbol 'ks_pcie_irq_eoi' was not declared. Should it be static?
Date: Mon, 27 Nov 2023 00:46:03 +0800 [thread overview]
Message-ID: <202311262318.Gbf4OPXP-lkp@intel.com> (raw)
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-6.1.y-wip
head: 07cbd0efc06ffff69b2b0c3d7d607b35829340c3
commit: 6aed116cd98bebc49ae9b7b6df299ca7a4da91f8 [4/64] PCI: keystone: Convert to using hierarchy domain for legacy interrupts
config: alpha-randconfig-r121-20231126 (https://download.01.org/0day-ci/archive/20231126/202311262318.Gbf4OPXP-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231126/202311262318.Gbf4OPXP-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/202311262318.Gbf4OPXP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/controller/dwc/pci-keystone.c:292:6: sparse: sparse: symbol 'ks_pcie_irq_eoi' was not declared. Should it be static?
>> drivers/pci/controller/dwc/pci-keystone.c:301:6: sparse: sparse: symbol 'ks_pcie_irq_enable' was not declared. Should it be static?
>> drivers/pci/controller/dwc/pci-keystone.c:310:6: sparse: sparse: symbol 'ks_pcie_irq_disable' was not declared. Should it be static?
vim +/ks_pcie_irq_eoi +292 drivers/pci/controller/dwc/pci-keystone.c
291
> 292 void ks_pcie_irq_eoi(struct irq_data *data)
293 {
294 struct keystone_pcie *ks_pcie = irq_data_get_irq_chip_data(data);
295 irq_hw_number_t hwirq = data->hwirq;
296
297 ks_pcie_app_writel(ks_pcie, IRQ_EOI, hwirq);
298 irq_chip_eoi_parent(data);
299 }
300
> 301 void ks_pcie_irq_enable(struct irq_data *data)
302 {
303 struct keystone_pcie *ks_pcie = irq_data_get_irq_chip_data(data);
304 irq_hw_number_t hwirq = data->hwirq;
305
306 ks_pcie_app_writel(ks_pcie, IRQ_ENABLE_SET(hwirq), INTx_EN);
307 irq_chip_enable_parent(data);
308 }
309
> 310 void ks_pcie_irq_disable(struct irq_data *data)
311 {
312 struct keystone_pcie *ks_pcie = irq_data_get_irq_chip_data(data);
313 irq_hw_number_t hwirq = data->hwirq;
314
315 ks_pcie_app_writel(ks_pcie, IRQ_ENABLE_CLR(hwirq), INTx_EN);
316 irq_chip_disable_parent(data);
317 }
318
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-26 16:48 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=202311262318.Gbf4OPXP-lkp@intel.com \
--to=lkp@intel.com \
--cc=a-verma1@ti.com \
--cc=kishon@ti.com \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vigneshr@ti.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.