llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: Re: [PATCH v3 1/3] dt-bindings: remoteproc: qcom: adsp: Add missing constrains for SDM660 ADSP
Date: Fri, 14 Nov 2025 05:21:39 +0800	[thread overview]
Message-ID: <202511140558.aJm7knAJ-lkp@intel.com> (raw)

In-Reply-To: <20251110-qcom-sdm660-cdsp-v3-1-cc3c37287e72@mainlining.org>
References: <20251110-qcom-sdm660-cdsp-v3-1-cc3c37287e72@mainlining.org>
TO: Nickolay Goppen <setotau@mainlining.org>
TO: Bjorn Andersson <andersson@kernel.org>
TO: Mathieu Poirier <mathieu.poirier@linaro.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Manivannan Sadhasivam <mani@kernel.org>
CC: linux-arm-msm@vger.kernel.org
CC: linux-remoteproc@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: ~postmarketos/upstreaming@lists.sr.ht
CC: linux@mainlining.org
CC: Nickolay Goppen <setotau@mainlining.org>

Hi Nickolay,

kernel test robot noticed the following build errors:

[auto build test ERROR on 93f3bab4310d4ff73027cc4f87174284d4977acf]

url:    https://github.com/intel-lab-lkp/linux/commits/Nickolay-Goppen/dt-bindings-remoteproc-qcom-adsp-Add-missing-constrains-for-SDM660-ADSP/20251111-023908
base:   93f3bab4310d4ff73027cc4f87174284d4977acf
patch link:    https://lore.kernel.org/r/20251110-qcom-sdm660-cdsp-v3-1-cc3c37287e72%40mainlining.org
patch subject: [PATCH v3 1/3] dt-bindings: remoteproc: qcom: adsp: Add missing constrains for SDM660 ADSP
config: riscv-randconfig-002-20251114 (https://download.01.org/0day-ci/archive/20251114/202511140558.aJm7knAJ-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 0bba1e76581bad04e7d7f09f5115ae5e2989e0d9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251114/202511140558.aJm7knAJ-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/202511140558.aJm7knAJ-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: vmlinux.a(drivers/pinctrl/pinconf-generic.o):(function pinconf_generic_dump_pins: .text+0x48): relocation R_RISCV_HI20 out of range: 531972 is not in [-524288, 524287]; references 'conf_items'
   >>> referenced by pinconf-generic.c
   >>> defined in vmlinux.a(drivers/pinctrl/pinconf-generic.o)
--
>> ld.lld: error: vmlinux.a(drivers/pinctrl/pinconf-generic.o):(function pinconf_generic_dump_pins: .text+0xac): relocation R_RISCV_HI20 out of range: 538219 is not in [-524288, 524287]; references '.L__unnamed_1'
   >>> referenced by pinconf-generic.c
   >>> defined in vmlinux.a(drivers/pinctrl/pinconf-generic.o)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-11-13 21:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202511140558.aJm7knAJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).