From: kernel test robot <lkp@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [rt-devel:linux-6.10.y-rt-rebase 63/93] kernel/printk/printk.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
Date: Thu, 30 May 2024 05:15:57 +0800 [thread overview]
Message-ID: <202405300545.mVqyyvyr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-6.10.y-rt-rebase
head: 6d20efa57a896036453f4b061ae22601ef61b494
commit: 127f3e5b794bd6fa90d4649318dd898455efa6d7 [63/93] printk: Provide threadprintk boot argument
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240530/202405300545.mVqyyvyr-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240530/202405300545.mVqyyvyr-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/202405300545.mVqyyvyr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/printk/printk.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
--
>> kernel/printk/nbcon.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
objdump-func vmlinux.o __jump_table:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-05-29 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 21:15 kernel test robot [this message]
2024-06-03 9:42 ` [rt-devel:linux-6.10.y-rt-rebase 63/93] kernel/printk/printk.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction John Ogness
2024-06-04 0:59 ` Yujie Liu
2024-06-04 9:44 ` Huacai Chen
2024-06-04 9:49 ` Tiezhu Yang
2024-06-04 10:03 ` Sebastian Andrzej Siewior
2024-06-04 12:09 ` Tiezhu Yang
2024-06-04 12:09 ` Xi Ruoyao
2024-06-04 15:17 ` Xi Ruoyao
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=202405300545.mVqyyvyr-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.