From: kernel test robot <lkp@intel.com>
To: Pingfan Liu <piliu@redhat.com>, linuxppc-dev@lists.ozlabs.org
Cc: Baoquan He <bhe@redhat.com>, Pingfan Liu <piliu@redhat.com>,
llvm@lists.linux.dev, kexec@lists.infradead.org,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Ming Lei <ming.lei@redhat.com>,
Wen Xiong <wenxiong@linux.ibm.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCHv6 1/3] powerpc/setup: Loosen the mapping between cpu logical id and its seq in dt
Date: Wed, 13 Sep 2023 02:50:29 +0800 [thread overview]
Message-ID: <202309130232.N2REwHBv-lkp@intel.com> (raw)
In-Reply-To: <20230911131855.40738-2-piliu@redhat.com>
Hi Pingfan,
kernel test robot noticed the following build errors:
[auto build test ERROR on powerpc/fixes]
[also build test ERROR on linus/master v6.6-rc1 next-20230912]
[cannot apply to powerpc/next]
[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/Pingfan-Liu/powerpc-setup-Loosen-the-mapping-between-cpu-logical-id-and-its-seq-in-dt/20230911-213042
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git fixes
patch link: https://lore.kernel.org/r/20230911131855.40738-2-piliu%40redhat.com
patch subject: [PATCHv6 1/3] powerpc/setup: Loosen the mapping between cpu logical id and its seq in dt
config: powerpc-randconfig-r032-20230912 (https://download.01.org/0day-ci/archive/20230913/202309130232.N2REwHBv-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230913/202309130232.N2REwHBv-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/202309130232.N2REwHBv-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: boot_cpu_hwid
>>> referenced by setup-common.c:0 (arch/powerpc/kernel/setup-common.c:0)
>>> arch/powerpc/kernel/setup-common.o:(smp_setup_cpu_maps) in archive vmlinux.a
>>> referenced by setup-common.c:0 (arch/powerpc/kernel/setup-common.c:0)
>>> arch/powerpc/kernel/setup-common.o:(smp_setup_cpu_maps) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-12 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 13:18 [PATCHv6 0/3] enable nr_cpus for powerpc Pingfan Liu
2023-09-11 13:18 ` [PATCHv6 1/3] powerpc/setup: Loosen the mapping between cpu logical id and its seq in dt Pingfan Liu
2023-09-12 18:50 ` kernel test robot [this message]
2023-09-11 13:18 ` [PATCHv6 2/3] powerpc/setup: Handle the case when boot_cpuid greater than nr_cpus Pingfan Liu
2023-09-11 13:18 ` [PATCHv6 3/3] powerpc/setup: alloc extra paca_ptrs to hold boot_cpuid Pingfan Liu
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=202309130232.N2REwHBv-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mahesh@linux.ibm.com \
--cc=ming.lei@redhat.com \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=piliu@redhat.com \
--cc=wenxiong@linux.ibm.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).