From: kernel test robot <lkp@intel.com>
To: Hans Zhang <18255117159@163.com>, lpieralisi@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.com, jingoohan1@gmail.com,
thomas.richard@bootlin.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans Zhang <18255117159@163.com>
Subject: Re: [v5 1/4] PCI: Introduce generic capability search functions
Date: Sat, 22 Mar 2025 04:05:39 +0800 [thread overview]
Message-ID: <202503220356.59PxEhDx-lkp@intel.com> (raw)
In-Reply-To: <20250321163803.391056-2-18255117159@163.com>
Hi Hans,
kernel test robot noticed the following build warnings:
[auto build test WARNING on a1cffe8cc8aef85f1b07c4464f0998b9785b795a]
url: https://github.com/intel-lab-lkp/linux/commits/Hans-Zhang/PCI-Introduce-generic-capability-search-functions/20250322-004312
base: a1cffe8cc8aef85f1b07c4464f0998b9785b795a
patch link: https://lore.kernel.org/r/20250321163803.391056-2-18255117159%40163.com
patch subject: [v5 1/4] PCI: Introduce generic capability search functions
config: arm-randconfig-001-20250322 (https://download.01.org/0day-ci/archive/20250322/202503220356.59PxEhDx-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250322/202503220356.59PxEhDx-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/202503220356.59PxEhDx-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/arm/mm/iomap.c:9:0:
include/linux/pci.h:2025:1: error: expected identifier or '(' before '{' token
{ return 0; }
^
include/linux/pci.h:2029:1: error: expected identifier or '(' before '{' token
{ return 0; }
^
In file included from arch/arm/mm/iomap.c:9:0:
>> include/linux/pci.h:2023:1: warning: 'pci_host_bridge_find_capability' declared 'static' but never defined [-Wunused-function]
pci_host_bridge_find_capability(void *priv, pci_host_bridge_read_cfg read_cfg,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/pci.h:2027:1: warning: 'pci_host_bridge_find_ext_capability' declared 'static' but never defined [-Wunused-function]
pci_host_bridge_find_ext_capability(void *priv,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +2023 include/linux/pci.h
2000
2001 static inline void pci_set_master(struct pci_dev *dev) { }
2002 static inline void pci_clear_master(struct pci_dev *dev) { }
2003 static inline int pci_enable_device(struct pci_dev *dev) { return -EIO; }
2004 static inline void pci_disable_device(struct pci_dev *dev) { }
2005 static inline int pcim_enable_device(struct pci_dev *pdev) { return -EIO; }
2006 static inline int pci_assign_resource(struct pci_dev *dev, int i)
2007 { return -EBUSY; }
2008 static inline int __must_check __pci_register_driver(struct pci_driver *drv,
2009 struct module *owner,
2010 const char *mod_name)
2011 { return 0; }
2012 static inline int pci_register_driver(struct pci_driver *drv)
2013 { return 0; }
2014 static inline void pci_unregister_driver(struct pci_driver *drv) { }
2015 static inline u8 pci_find_capability(struct pci_dev *dev, int cap)
2016 { return 0; }
2017 static inline u8 pci_find_next_capability(struct pci_dev *dev, u8 post, int cap)
2018 { return 0; }
2019 static inline u16 pci_find_ext_capability(struct pci_dev *dev, int cap)
2020 { return 0; }
2021 typedef u32 (*pci_host_bridge_read_cfg)(void *priv, int where, int size);
2022 static inline u8
> 2023 pci_host_bridge_find_capability(void *priv, pci_host_bridge_read_cfg read_cfg,
2024 u8 cap);
> 2025 { return 0; }
2026 static inline u16
> 2027 pci_host_bridge_find_ext_capability(void *priv,
2028 pci_host_bridge_read_cfg read_cfg, u8 cap);
> 2029 { return 0; }
2030 static inline u64 pci_get_dsn(struct pci_dev *dev)
2031 { return 0; }
2032
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-21 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 16:37 [v5 0/4] Introduce generic capability search functions Hans Zhang
2025-03-21 16:38 ` [v5 1/4] PCI: " Hans Zhang
2025-03-21 17:06 ` Lukas Wunner
2025-03-22 15:47 ` Hans Zhang
2025-03-22 16:11 ` Lukas Wunner
2025-03-23 15:36 ` Hans Zhang
2025-03-21 20:05 ` kernel test robot [this message]
2025-03-21 20:57 ` kernel test robot
2025-03-21 20:57 ` kernel test robot
2025-03-21 16:38 ` [v5 2/4] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities Hans Zhang
2025-03-21 16:38 ` [v5 3/4] PCI: cadence: " Hans Zhang
2025-03-21 16:38 ` [v5 4/4] PCI: cadence: Use cdns_pcie_find_*capability to avoid hardcode Hans Zhang
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=202503220356.59PxEhDx-lkp@intel.com \
--to=lkp@intel.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=thomas.richard@bootlin.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.