From: kernel test robot <lkp@intel.com>
To: Chengwen Feng <fengchengwen@huawei.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com
Cc: oe-kbuild-all@lists.linux.dev, linux-acpi@vger.kernel.org,
rafael@kernel.org, lenb@kernel.org, wei.huang2@amd.com,
Eric.VanTassell@amd.com, jonathan.cameron@huawei.com,
wangzhou1@hisilicon.com, wanghuiqiang@huawei.com,
liuyonglong@huawei.com, Chengwen Feng <fengchengwen@huawei.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] PCI/TPH: Fix get cpu steer-tag fail on ARM64 platform
Date: Thu, 5 Mar 2026 07:18:49 +0800 [thread overview]
Message-ID: <202603050711.whqDobKh-lkp@intel.com> (raw)
In-Reply-To: <20260303003625.39035-1-fengchengwen@huawei.com>
Hi Chengwen,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus rafael-pm/linux-next rafael-pm/bleeding-edge linus/master v7.0-rc2 next-20260304]
[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/Chengwen-Feng/PCI-TPH-Fix-get-cpu-steer-tag-fail-on-ARM64-platform/20260303-084305
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20260303003625.39035-1-fengchengwen%40huawei.com
patch subject: [PATCH] PCI/TPH: Fix get cpu steer-tag fail on ARM64 platform
config: x86_64-randconfig-r072-20260305 (https://download.01.org/0day-ci/archive/20260305/202603050711.whqDobKh-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9004-gb810ac53
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260305/202603050711.whqDobKh-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/202603050711.whqDobKh-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/acpi/processor_core.c: In function 'acpi_get_cpu_acpi_id':
>> drivers/acpi/processor_core.c:344:16: error: implicit declaration of function 'cpu_acpi_id' [-Wimplicit-function-declaration]
344 | return cpu_acpi_id(cpu);
| ^~~~~~~~~~~
vim +/cpu_acpi_id +344 drivers/acpi/processor_core.c
337
338 #ifdef CONFIG_ARCH_HAS_GET_CPU_ACPI_ID_API
339 unsigned int acpi_get_cpu_acpi_id(unsigned int cpu)
340 {
341 if (cpu >= nr_cpu_ids)
342 return 0;
343 #ifdef CONFIG_X86
> 344 return cpu_acpi_id(cpu);
345 #elif CONFIG_ARM64
346 return get_acpi_id_for_cpu(cpu);
347 #endif
348 }
349 #endif /* CONFIG_ARCH_HAS_GET_CPU_ACPI_ID_API */
350
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-04 23:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 0:36 [PATCH] PCI/TPH: Fix get cpu steer-tag fail on ARM64 platform Chengwen Feng
2026-03-03 19:02 ` Bjorn Helgaas
2026-03-04 9:28 ` fengchengwen
2026-03-04 15:38 ` Bjorn Helgaas
2026-03-05 8:40 ` fengchengwen
2026-03-04 13:50 ` kernel test robot
2026-03-04 23:18 ` kernel test robot [this message]
2026-03-05 0:02 ` kernel test robot
2026-03-05 1:29 ` kernel test robot
2026-03-05 8:36 ` [PATCH v2] " Chengwen Feng
2026-03-05 8:53 ` Huacai Chen
2026-03-05 9:07 ` fengchengwen
2026-03-05 14:54 ` Jonathan Cameron
2026-03-06 2:20 ` fengchengwen
2026-03-06 2:19 ` [PATCH v3] " Chengwen Feng
2026-03-06 10:01 ` Jonathan Cameron
2026-03-09 4:18 ` fengchengwen
2026-03-09 4:16 ` [PATCH v4 0/2] " Chengwen Feng
2026-03-09 4:16 ` [PATCH v4 1/2] ACPI: Rename get_acpi_id_for_cpu() to acpi_get_cpu_acpi_id() on non-x86 Chengwen Feng
2026-03-09 10:30 ` Jonathan Cameron
2026-03-09 13:29 ` Huacai Chen
2026-03-10 3:29 ` fengchengwen
2026-03-09 4:16 ` [PATCH v4 2/2] PCI/TPH: Fix get cpu steer-tag fail on ARM64 platform Chengwen Feng
2026-03-09 10:59 ` Jonathan Cameron
2026-03-09 10:28 ` [PATCH v4 0/2] " Jonathan Cameron
2026-03-10 3:26 ` fengchengwen
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=202603050711.whqDobKh-lkp@intel.com \
--to=lkp@intel.com \
--cc=Eric.VanTassell@amd.com \
--cc=bhelgaas@google.com \
--cc=fengchengwen@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wanghuiqiang@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=wei.huang2@amd.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