From: kernel test robot <lkp@intel.com>
To: Alistair Francis <alistair@alistair23.me>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
Jonathan.Cameron@huawei.com, lukas@wunner.de
Cc: oe-kbuild-all@lists.linux.dev, alex.williamson@redhat.com,
christian.koenig@amd.com, kch@nvidia.com,
gregkh@linuxfoundation.org, logang@deltatee.com,
linux-kernel@vger.kernel.org, alistair23@gmail.com,
chaitanyak@nvidia.com, rdunlap@infradead.org,
Alistair Francis <alistair@alistair23.me>
Subject: Re: [PATCH v17 3/4] PCI/DOE: Expose the DOE features via sysfs
Date: Fri, 7 Mar 2025 22:10:47 +0800 [thread overview]
Message-ID: <202503072119.bmT7zRPN-lkp@intel.com> (raw)
In-Reply-To: <20250306075211.1855177-3-alistair@alistair23.me>
Hi Alistair,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/next]
[also build test WARNING on pci/for-linus linus/master v6.14-rc5 next-20250307]
[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/Alistair-Francis/PCI-DOE-Rename-Discovery-Response-Data-Object-Contents-to-type/20250306-155550
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20250306075211.1855177-3-alistair%40alistair23.me
patch subject: [PATCH v17 3/4] PCI/DOE: Expose the DOE features via sysfs
config: microblaze-randconfig-r111-20250307 (https://download.01.org/0day-ci/archive/20250307/202503072119.bmT7zRPN-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250307/202503072119.bmT7zRPN-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/202503072119.bmT7zRPN-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/doe.c:109:1: sparse: sparse: symbol 'dev_attr_doe_discovery' was not declared. Should it be static?
vim +/dev_attr_doe_discovery +109 drivers/pci/doe.c
101
102 #ifdef CONFIG_SYSFS
103 static ssize_t doe_discovery_show(struct device *dev,
104 struct device_attribute *attr,
105 char *buf)
106 {
107 return sysfs_emit(buf, "0001:00\n");
108 }
> 109 DEVICE_ATTR_RO(doe_discovery);
110
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-07 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 7:52 [PATCH v17 1/4] PCI/DOE: Rename DOE protocol to feature Alistair Francis
2025-03-06 7:52 ` [PATCH v17 2/4] PCI/DOE: Rename Discovery Response Data Object Contents to type Alistair Francis
2025-03-06 7:52 ` [PATCH v17 3/4] PCI/DOE: Expose the DOE features via sysfs Alistair Francis
2025-03-07 12:05 ` kernel test robot
2025-03-07 14:10 ` kernel test robot [this message]
2025-03-07 15:18 ` kernel test robot
2025-03-07 16:01 ` kernel test robot
2025-03-21 21:41 ` Bjorn Helgaas
2025-03-24 3:02 ` Alistair Francis
2025-03-06 7:52 ` [PATCH v17 4/4] PCI/DOE: Allow enabling DOE without CXL Alistair Francis
2025-03-06 18:55 ` [PATCH v17 1/4] PCI/DOE: Rename DOE protocol to feature 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=202503072119.bmT7zRPN-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=bhelgaas@google.com \
--cc=chaitanyak@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=lukas@wunner.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
/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