From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [rafael-pm:bleeding-edge 2/5] ld.lld: error: vmlinux.a(init/main.o):(function __traceiter_initcall_level: .text+0x8): relocation R_RISCV_HI20 out of range: 528384 is not in [-524288, 524287]; references '__tracepoint_initcall_level'
Date: Tue, 12 Sep 2023 14:30:34 +0800 [thread overview]
Message-ID: <202309121434.B34VzSZM-lkp@intel.com> (raw)
CC: linux-acpi@vger.kernel.org
CC: devel@acpica.org
CC: linux-pm@vger.kernel.org
TO: "Rafael J. Wysocki" <rjw@rjwysocki.net>
CC: Michal Wilczynski <michal.wilczynski@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head: eb9b927bbb5841d2ff0f92548a5d7c724d2692ee
commit: ebc7abb35b258152d4a424f89d7c03db1d7ce61c [2/5] thermal: Constify the trip argument of the .get_trend() zone callback
config: riscv-randconfig-r005-20230912 (https://download.01.org/0day-ci/archive/20230912/202309121434.B34VzSZM-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/20230912/202309121434.B34VzSZM-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/202309121434.B34VzSZM-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: vmlinux.a(init/main.o):(function __traceiter_initcall_level: .text+0x8): relocation R_RISCV_HI20 out of range: 528384 is not in [-524288, 524287]; references '__tracepoint_initcall_level'
>>> referenced by main.c
>>> defined in vmlinux.a(init/main.o)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-12 6:40 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=202309121434.B34VzSZM-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