From: kernel test robot <lkp@intel.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
rostedt@goodmis.org, lukas@wunner.de, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, helgaas@kernel.org,
ilpo.jarvinen@linux.intel.com, mattc@purestorage.com,
Jonathan.Cameron@huawei.com
Cc: oe-kbuild-all@lists.linux.dev, bhelgaas@google.com,
tony.luck@intel.com, bp@alien8.de, xueshuai@linux.alibaba.com,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
oleg@redhat.com, naveen@kernel.org, davem@davemloft.net,
mark.rutland@arm.com, peterz@infradead.org,
tianruidong@linux.alibaba.com
Subject: Re: [PATCH v12 2/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes
Date: Wed, 15 Oct 2025 12:49:24 +0800 [thread overview]
Message-ID: <202510151212.ifOhr1Ak-lkp@intel.com> (raw)
In-Reply-To: <20251014123159.57764-3-xueshuai@linux.alibaba.com>
Hi Shuai,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v6.18-rc1 next-20251014]
[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/Shuai-Xue/PCI-trace-Add-a-generic-RAS-tracepoint-for-hotplug-event/20251014-203432
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20251014123159.57764-3-xueshuai%40linux.alibaba.com
patch subject: [PATCH v12 2/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes
config: sparc-randconfig-001-20251015 (https://download.01.org/0day-ci/archive/20251015/202510151212.ifOhr1Ak-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251015/202510151212.ifOhr1Ak-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/202510151212.ifOhr1Ak-lkp@intel.com/
All errors (new ones prefixed by >>):
sparc64-linux-ld: drivers/pci/trace.o: in function `trace_raw_output_pcie_link_event':
trace.c:(.text+0x1dc): undefined reference to `pci_speed_string'
>> sparc64-linux-ld: trace.c:(.text+0x1ec): undefined reference to `pci_speed_string'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-15 4:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 12:31 [PATCH v12 0/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-10-14 12:31 ` [PATCH v12 1/3] PCI: trace: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-10-14 15:40 ` Steven Rostedt
2025-10-15 2:35 ` Shuai Xue
2025-10-15 6:29 ` Shuai Xue
2025-10-15 14:37 ` Steven Rostedt
2025-10-20 1:32 ` Shuai Xue
2025-10-20 15:30 ` Steven Rostedt
2025-10-21 1:50 ` Shuai Xue
2025-10-14 12:31 ` [PATCH v12 2/3] PCI: trace: Add a RAS tracepoint to monitor link speed changes Shuai Xue
2025-10-15 4:49 ` kernel test robot [this message]
2025-10-14 12:31 ` [PATCH v12 3/3] Documentation: tracing: Add documentation about PCI tracepoints Shuai Xue
2025-10-14 14:40 ` Ilpo Järvinen
2025-10-15 2:36 ` Shuai Xue
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=202510151212.ifOhr1Ak-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattc@purestorage.com \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.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).