From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>
Subject: [s390:features 97/98] Unsupported relocation type: 21
Date: Thu, 22 Feb 2024 14:42:01 +0800 [thread overview]
Message-ID: <202402221404.T2TGs8El-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features
head: 4a5993287467d2d0401503256dc9d2690c7f2020
commit: 778666df60f0d96f215e33e27448de47a2207fb3 [97/98] s390: compile relocatable kernel without -fPIE
config: s390-randconfig-002-20231016 (https://download.01.org/0day-ci/archive/20240222/202402221404.T2TGs8El-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240222/202402221404.T2TGs8El-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/202402221404.T2TGs8El-lkp@intel.com/
All errors (new ones prefixed by >>):
>> Unsupported relocation type: 21
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-02-22 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 6:42 kernel test robot [this message]
2024-02-22 17:37 ` [s390:features 97/98] Unsupported relocation type: 21 Josh Poimboeuf
2024-02-23 9:50 ` Yujie Liu
2024-02-23 10:03 ` Sumanth Korikkar
2024-02-23 10:19 ` Sumanth Korikkar
2024-02-23 23:59 ` Josh Poimboeuf
2024-02-26 10:54 ` Sumanth Korikkar
2024-02-26 12:55 ` Sumanth Korikkar
2024-03-07 15:28 ` Sumanth Korikkar
2024-03-07 15:38 ` Sumanth Korikkar
2024-03-07 15:52 ` Vasily Gorbik
2024-03-07 16:13 ` Heiko Carstens
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=202402221404.T2TGs8El-lkp@intel.com \
--to=lkp@intel.com \
--cc=hca@linux.ibm.com \
--cc=jpoimboe@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sumanthk@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 read-only IMAP folder(s) and NNTP newsgroup(s).