From: kernel test robot <lkp@intel.com>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
Dan Carpenter <error27@gmail.com>
Subject: [linux-next:master 2357/7423] drivers/bluetooth/hci_vhci.o: warning: objtool: .text: unexpected end of section
Date: Sat, 1 Mar 2025 12:30:18 +0800 [thread overview]
Message-ID: <202503011220.Y2e5vz4w-lkp@intel.com> (raw)
Hi Ethan,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c0eb65494e59d9834af7cbad983629e9017b25a1
commit: 3b147be9ef08247bb74a801b4e95f9a626a27322 [2357/7423] hamradio: baycom: replace strcpy() with strscpy()
config: x86_64-buildonly-randconfig-006-20250301 (https://download.01.org/0day-ci/archive/20250301/202503011220.Y2e5vz4w-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250301/202503011220.Y2e5vz4w-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/202503011220.Y2e5vz4w-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/bluetooth/hci_vhci.o: warning: objtool: .text: unexpected end of section
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-01 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 4:30 kernel test robot [this message]
2025-03-01 16:15 ` [linux-next:master 2357/7423] drivers/bluetooth/hci_vhci.o: warning: objtool: .text: unexpected end of section Ethan Carter Edwards
2025-03-02 12:35 ` Dan Carpenter
2025-03-02 21:10 ` Nathan Chancellor
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=202503011220.Y2e5vz4w-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=ethan@ethancedwards.com \
--cc=kuba@kernel.org \
--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 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.