From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [tglx-devel:depthtracking 28/38] arch/x86/entry/entry_64.o: warning: objtool: .altinstr_replacement+0x15: unsupported relocation in alternatives section
Date: Fri, 15 Jul 2022 00:21:32 +0800 [thread overview]
Message-ID: <202207150029.zuZ1vOEj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git depthtracking
head: 81d2c1b17a61bfeca4b92a5d6e1fb6f5ff464826
commit: b05c8cdb2f065b83900983321afc3d449908003c [28/38] x86/retbleed: Add SKL return thunk
config: x86_64-randconfig-m001 (https://download.01.org/0day-ci/archive/20220715/202207150029.zuZ1vOEj-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git/commit/?id=b05c8cdb2f065b83900983321afc3d449908003c
git remote add tglx-devel https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git
git fetch --no-tags tglx-devel depthtracking
git checkout b05c8cdb2f065b83900983321afc3d449908003c
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/entry/entry_64.o: warning: objtool: .altinstr_replacement+0x15: unsupported relocation in alternatives section
--
>> arch/x86/entry/entry_64_compat.o: warning: objtool: .altinstr_replacement+0x15: unsupported relocation in alternatives section
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-14 16: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=202207150029.zuZ1vOEj-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®