From: Hanjun Guo <guohanjun@huawei.com>
To: kernel test robot <lkp@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
<linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 4/4] ARM64: ACPI: Move the NUMA code to drivers/acpi/arm64/
Date: Mon, 12 Aug 2024 11:46:09 +0800 [thread overview]
Message-ID: <8be9d042-3e57-8458-271f-d213ba519bd4@huawei.com> (raw)
In-Reply-To: <202408121026.c3mDLUsP-lkp@intel.com>
On 2024/8/12 11:02, kernel test robot wrote:
> Hi Hanjun,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on rafael-pm/linux-next rafael-pm/bleeding-edge linus/master v6.11-rc3 next-20240809]
> [cannot apply to arm-perf/for-next/perf]
> [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/Hanjun-Guo/ARM64-ACPI-Remove-the-leftover-acpi_init_cpus/20240811-122442
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> patch link: https://lore.kernel.org/r/20240811042303.3498761-5-guohanjun%40huawei.com
> patch subject: [PATCH v2 4/4] ARM64: ACPI: Move the NUMA code to drivers/acpi/arm64/
> config: arm64-randconfig-001-20240812 (https://download.01.org/0day-ci/archive/20240812/202408121026.c3mDLUsP-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 14.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240812/202408121026.c3mDLUsP-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/202408121026.c3mDLUsP-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> aarch64-linux-ld: Unexpected GOT/PLT entries detected!
> aarch64-linux-ld: Unexpected run-time procedure linkages detected!
> aarch64-linux-ld: arch/arm64/kernel/smp.o: in function `smp_init_cpus':
>>> arch/arm64/kernel/smp.c:669:(.init.text+0x424): undefined reference to `acpi_map_cpus_to_nodes'
Good catch, I missed the random config which CONFIG_NUMA is not set.
Thanks
Hanjun
prev parent reply other threads:[~2024-08-12 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 4:22 [PATCH v2 0/4] Cleanups for ARM64 ACPI Hanjun Guo
2024-08-11 4:23 ` [PATCH v2 1/4] ARM64: ACPI: Remove the leftover acpi_init_cpus() Hanjun Guo
2024-08-11 4:23 ` [PATCH v2 2/4] ARM64: ACPI: Remove the leftover arm64_acpi_numa_init() Hanjun Guo
2024-08-11 4:23 ` [PATCH v2 3/4] ARM64: ACPI: Make acpi_numa_get_nid() invisible to kernel/smp.c Hanjun Guo
2024-08-11 4:23 ` [PATCH v2 4/4] ARM64: ACPI: Move the NUMA code to drivers/acpi/arm64/ Hanjun Guo
2024-08-12 3:02 ` kernel test robot
2024-08-12 3:46 ` Hanjun Guo [this message]
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=8be9d042-3e57-8458-271f-d213ba519bd4@huawei.com \
--to=guohanjun@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=lpieralisi@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox