From: kernel test robot <lkp@intel.com>
To: "Manivannan Sadhasivam via B4 Relay"
<devnull+manivannan.sadhasivam.linaro.org@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH v2 1/3] PCI: Add sysfs support for exposing PTM context
Date: Thu, 27 Mar 2025 05:18:39 +0800 [thread overview]
Message-ID: <202503270447.SYoXEBQd-lkp@intel.com> (raw)
In-Reply-To: <20250324-pcie-ptm-v2-1-c7d8c3644b4a@linaro.org>
Hi Manivannan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 1f5a69f1b3132054d8d82b8d7546d0af6a2ed4f6]
url: https://github.com/intel-lab-lkp/linux/commits/Manivannan-Sadhasivam-via-B4-Relay/PCI-Add-sysfs-support-for-exposing-PTM-context/20250324-181039
base: 1f5a69f1b3132054d8d82b8d7546d0af6a2ed4f6
patch link: https://lore.kernel.org/r/20250324-pcie-ptm-v2-1-c7d8c3644b4a%40linaro.org
patch subject: [PATCH v2 1/3] PCI: Add sysfs support for exposing PTM context
config: i386-randconfig-061-20250326 (https://download.01.org/0day-ci/archive/20250327/202503270447.SYoXEBQd-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250327/202503270447.SYoXEBQd-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/202503270447.SYoXEBQd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pci/pcie/ptm.c:13:15: sparse: sparse: symbol 'ptm_device' was not declared. Should it be static?
vim +/ptm_device +13 drivers/pci/pcie/ptm.c
12
> 13 struct device *ptm_device;
14
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-26 21:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 10:04 [PATCH v2 0/3] PCI: Add PTM sysfs support Manivannan Sadhasivam
2025-03-24 10:04 ` Manivannan Sadhasivam via B4 Relay
2025-03-24 10:04 ` [PATCH v2 1/3] PCI: Add sysfs support for exposing PTM context Manivannan Sadhasivam
2025-03-24 10:04 ` Manivannan Sadhasivam via B4 Relay
2025-03-24 13:01 ` Ilpo Järvinen
2025-04-07 7:36 ` Manivannan Sadhasivam
2025-03-24 16:28 ` Bjorn Helgaas
2025-04-07 7:44 ` Manivannan Sadhasivam
2025-04-07 16:53 ` Bjorn Helgaas
2025-03-26 21:18 ` kernel test robot [this message]
2025-03-24 10:04 ` [PATCH v2 2/3] PCI: dwc: Add sysfs support for " Manivannan Sadhasivam
2025-03-24 10:04 ` Manivannan Sadhasivam via B4 Relay
2025-03-24 14:06 ` kernel test robot
2025-03-26 21:42 ` kernel test robot
2025-03-24 10:04 ` [PATCH v2 3/3] PCI: qcom-ep: Mask PTM_UPDATING interrupt Manivannan Sadhasivam
2025-03-24 10:04 ` Manivannan Sadhasivam via B4 Relay
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=202503270447.SYoXEBQd-lkp@intel.com \
--to=lkp@intel.com \
--cc=devnull+manivannan.sadhasivam.linaro.org@kernel.org \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--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 \
/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.