From: kernel test robot <lkp@intel.com>
To: Hans Zhang <18255117159@163.com>, lpieralisi@kernel.org
Cc: llvm@lists.linux.dev, 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:57:27 +0800 [thread overview]
Message-ID: <202503220409.NDrvLkQF-lkp@intel.com> (raw)
In-Reply-To: <20250321163803.391056-2-18255117159@163.com>
Hi Hans,
kernel test robot noticed the following build errors:
[auto build test ERROR 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: arm64-randconfig-001-20250322 (https://download.01.org/0day-ci/archive/20250322/202503220409.NDrvLkQF-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project c2692afc0a92cd5da140dfcdfff7818a5b8ce997)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250322/202503220409.NDrvLkQF-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/202503220409.NDrvLkQF-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/hv/vmbus_drv.c:38:
>> include/linux/pci.h:2025:1: error: expected identifier or '('
2025 | { return 0; }
| ^
include/linux/pci.h:2029:1: error: expected identifier or '('
2029 | { return 0; }
| ^
drivers/hv/vmbus_drv.c:1928:42: warning: shift count >= width of type [-Wshift-count-overflow]
1928 | dma_set_mask(&child_device_obj->device, DMA_BIT_MASK(64));
| ^~~~~~~~~~~~~~~~
include/linux/dma-mapping.h:73:54: note: expanded from macro 'DMA_BIT_MASK'
73 | #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
| ^ ~~~
1 warning and 2 errors generated.
vim +2025 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
parent reply other threads:[~2025-03-21 20:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250321163803.391056-2-18255117159@163.com>]
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=202503220409.NDrvLkQF-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=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox