From: kernel test robot <lkp@intel.com>
To: Lizhi Hou <lizhi.hou@amd.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Lizhi Hou <lizhi.hou@amd.com>,
max.zhen@amd.com, sonal.santan@amd.com,
stefano.stabellini@xilinx.com
Subject: Re: [PATCH V12 5/5] of: unittest: Add pci_dt_testdrv pci driver
Date: Mon, 14 Aug 2023 09:44:14 +0800 [thread overview]
Message-ID: <202308140955.QY7JaDK3-lkp@intel.com> (raw)
In-Reply-To: <1690564018-11142-6-git-send-email-lizhi.hou@amd.com>
Hi Lizhi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus robh/for-next linus/master v6.5-rc6 next-20230809]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lizhi-Hou/of-dynamic-Add-interfaces-for-creating-device-node-dynamically/20230729-010934
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/1690564018-11142-6-git-send-email-lizhi.hou%40amd.com
patch subject: [PATCH V12 5/5] of: unittest: Add pci_dt_testdrv pci driver
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20230814/202308140955.QY7JaDK3-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230814/202308140955.QY7JaDK3-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/202308140955.QY7JaDK3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/of/unittest.c:3737:5: sparse: sparse: symbol 'of_unittest_pci_dev_num' was not declared. Should it be static?
>> drivers/of/unittest.c:3738:5: sparse: sparse: symbol 'of_unittest_pci_child_num' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-14 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:06 [PATCH V12 0/5] Generate device tree node for pci devices Lizhi Hou
2023-07-28 17:06 ` [PATCH V12 1/5] of: dynamic: Add interfaces for creating device node dynamically Lizhi Hou
2023-07-28 17:06 ` [PATCH V12 2/5] PCI: Create device tree node for bridge Lizhi Hou
2023-07-28 17:06 ` [PATCH V12 3/5] PCI: Add quirks to generate device tree node for Xilinx Alveo U50 Lizhi Hou
2023-07-28 17:06 ` [PATCH V12 4/5] of: overlay: Extend of_overlay_fdt_apply() to specify the target node Lizhi Hou
2023-07-28 17:06 ` [PATCH V12 5/5] of: unittest: Add pci_dt_testdrv pci driver Lizhi Hou
2023-08-14 1:44 ` kernel test robot [this message]
2023-08-14 22:28 ` kernel test robot
2023-08-09 22:57 ` [PATCH V12 0/5] Generate device tree node for pci devices Bjorn Helgaas
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=202308140955.QY7JaDK3-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sonal.santan@amd.com \
--cc=stefano.stabellini@xilinx.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 NNTP newsgroup(s).