From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [peterz-queue:x86/kvm 3/11] net/mac80211/mac80211.o: warning: objtool: __SCT__tp_func_drv_return_void+0x0: retpoline_safe hint not an indirect jump/call/ret/nop
Date: Wed, 6 Dec 2023 02:39:45 +0800 [thread overview]
Message-ID: <202312060228.RHJs2gLq-lkp@intel.com> (raw)
TO: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/kvm
head: bd8e1c4c02ac085925674bddccb989e2d7d6cc2d
commit: b7a510b43b1833fc6b0543c0295970c1dd87fbde [3/11] objtool: Convert ANNOTATE_RETPOLINE_SAFE to ANNOTATE
config: x86_64-randconfig-003-20231203 (https://download.01.org/0day-ci/archive/20231206/202312060228.RHJs2gLq-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312060228.RHJs2gLq-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/202312060228.RHJs2gLq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/mac80211/mac80211.o: warning: objtool: __SCT__tp_func_drv_return_void+0x0: retpoline_safe hint not an indirect jump/call/ret/nop
--
>> drivers/cxl/core/cxl_core.o: warning: objtool: __SCT__tp_func_cxl_aer_uncorrectable_error+0x0: retpoline_safe hint not an indirect jump/call/ret/nop
objdump-func vmlinux.o __SCT__tp_func_drv_return_void:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-05 18: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=202312060228.RHJs2gLq-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