From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [jsarha:topic/chromeos-4.19-s0ix 9741/9999] net/bluetooth/l2cap_core.o: warning: objtool: l2cap_chan_close()+0x94: can't find switch jump table
Date: Mon, 5 Sep 2022 23:38:26 +0800 [thread overview]
Message-ID: <202209052358.SPSbkrWh-lkp@intel.com> (raw)
CC: linux-kernel@vger.kernel.org
TO: Archie Pusaka <apusaka@chromium.org>
CC: "Shyh-In Hwang" <josephsih@chromium.org>
CC: Sonny Sasaka <sonnysasaka@chromium.org>
tree: https://github.com/jsarha/linux topic/chromeos-4.19-s0ix
head: 430bdaa0a8c38697780f45a148964d71951df11f
commit: 9b30b4dd29c7f6b53f53076d7339e112c308f05e [9741/9999] CHROMIUM: bluetooth: enable turn on/off debug logs at runtime
config: x86_64-randconfig-a013-20220905 (https://download.01.org/0day-ci/archive/20220905/202209052358.SPSbkrWh-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/jsarha/linux/commit/9b30b4dd29c7f6b53f53076d7339e112c308f05e
git remote add jsarha https://github.com/jsarha/linux
git fetch --no-tags jsarha topic/chromeos-4.19-s0ix
git checkout 9b30b4dd29c7f6b53f53076d7339e112c308f05e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash net/
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 >>):
>> net/bluetooth/l2cap_core.o: warning: objtool: l2cap_chan_close()+0x94: can't find switch jump table
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-05 15:38 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=202209052358.SPSbkrWh-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@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;
as well as URLs for NNTP newsgroup(s).