From: Lee Jones <lee@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Lukas Bulwahn <lbulwahn@redhat.com>,
Samuel Kayode <samuel.kayode@savoirfairelinux.com>,
imx@lists.linux.dev, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, Frank Li <Frank.Li@nxp.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Sean Nyekjaer <sean@geanix.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in NXP PF1550 PMIC MFD DRIVER
Date: Mon, 3 Nov 2025 15:23:21 +0000 [thread overview]
Message-ID: <20251103152321.GA8064@google.com> (raw)
In-Reply-To: <202511011641.mVLMVN8V-lkp@intel.com>
On Sat, 01 Nov 2025, kernel test robot wrote:
> Hi Lukas,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on next-20251029]
> [cannot apply to lee-leds/for-leds-next linus/master v6.18-rc3 v6.18-rc2 v6.18-rc1 v6.18-rc3]
> [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/Lukas-Bulwahn/MAINTAINERS-adjust-file-entry-in-NXP-PF1550-PMIC-MFD-DRIVER/20251029-184717
> base: next-20251029
> patch link: https://lore.kernel.org/r/20251029104228.95498-1-lukas.bulwahn%40redhat.com
> patch subject: [PATCH] MAINTAINERS: adjust file entry in NXP PF1550 PMIC MFD DRIVER
> config: powerpc-randconfig-002-20251101 (https://download.01.org/0day-ci/archive/20251101/202511011641.mVLMVN8V-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project d1c086e82af239b245fe8d7832f2753436634990)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251101/202511011641.mVLMVN8V-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/202511011641.mVLMVN8V-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> ld.lld: error: relocation R_PPC_ADDR16_HI cannot be used against symbol 'init_task'; recompile with -fPIC
> >>> defined in vmlinux.a(init/init_task.o)
> >>> referenced by head_85xx.S:222 (arch/powerpc/kernel/head_85xx.S:222)
> >>> arch/powerpc/kernel/head_85xx.o:(.head.text+0x41a) in archive vmlinux.a
> --
> >> ld.lld: error: relocation R_PPC_ADDR16_LO cannot be used against symbol 'init_task'; recompile with -fPIC
> >>> defined in vmlinux.a(init/init_task.o)
> >>> referenced by head_85xx.S:223 (arch/powerpc/kernel/head_85xx.S:223)
> >>> arch/powerpc/kernel/head_85xx.o:(.head.text+0x41e) in archive vmlinux.a
> --
> >> ld.lld: error: relocation R_PPC_ADDR16_HI cannot be used against symbol 'init_thread_union'; recompile with -fPIC
> >>> defined in ./arch/powerpc/kernel/vmlinux.lds:146
> >>> referenced by head_85xx.S:230 (arch/powerpc/kernel/head_85xx.S:230)
> >>> arch/powerpc/kernel/head_85xx.o:(.head.text+0x42a) in archive vmlinux.a
What is all of this nonsense?
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-11-03 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 10:42 [PATCH] MAINTAINERS: adjust file entry in NXP PF1550 PMIC MFD DRIVER Lukas Bulwahn
2025-10-30 1:53 ` Samuel Kayode
2025-11-01 8:49 ` kernel test robot
2025-11-03 15:23 ` Lee Jones [this message]
2025-11-05 1:46 ` Philip Li
2025-11-13 15:50 ` (subset) " Lee Jones
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=20251103152321.GA8064@google.com \
--to=lee@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=lukas.bulwahn@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=samuel.kayode@savoirfairelinux.com \
--cc=sean@geanix.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