From: kernel test robot <lkp@intel.com>
To: Hilda Wu <hildawu@realtek.com>, marcel@holtmann.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, alex_lu@realsil.com.cn,
jason_mao@realsil.com.cn, zoey_zhou@realsil.com.cn,
max.chou@realtek.com, kidman@realtek.com,
arunr@valvesoftware.com
Subject: Re: [PATCH v10 1/2] Bluetooth: btrtl: Add firmware format v3 support
Date: Sat, 21 Nov 2026 22:35:14 +0800 [thread overview]
Message-ID: <202611212209.wBWI3Z2q-lkp@intel.com> (raw)
In-Reply-To: <20261120082636.3834168-2-hildawu@realtek.com>
Hi Hilda,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth/master]
[also build test ERROR on bluetooth-next/master]
[cannot apply to linus/master v7.4-rc3 next-20261119]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Hilda-Wu/Bluetooth-btrtl-Add-firmware-format-v3-support/20261120-162635
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
patch link: https://lore.kernel.org/r/20261120082636.3834168-2-hildawu%40realtek.com
patch subject: [PATCH v10 1/2] Bluetooth: btrtl: Add firmware format v3 support
config: i386-randconfig-1003-20261121 (https://download.01.org/0day-ci/archive/20261121/202611212209.wBWI3Z2q-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261121/202611212209.wBWI3Z2q-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/202611212209.wBWI3Z2q-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: btrtl_recv_event
>>> referenced by btusb_main.c:2995 (drivers/bluetooth/btusb_main.c:2995)
>>> drivers/bluetooth/btusb_main.o:(btusb_recv_event_realtek) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-11-21 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 8:26 [PATCH v10 0/2] Bluetooth: btrtl: Add firmware format v3 support and RTL8922D Hilda Wu
2026-11-20 8:26 ` [PATCH v10 1/2] Bluetooth: btrtl: Add firmware format v3 support Hilda Wu
2026-11-20 13:26 ` Bluetooth: btrtl: Add firmware format v3 support and RTL8922D bluez.test.bot
2026-11-21 14:35 ` kernel test robot [this message]
2026-11-20 8:26 ` [PATCH v10 2/2] Bluetooth: btrtl: Add the support for RTL8922D Hilda Wu
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=202611212209.wBWI3Z2q-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex_lu@realsil.com.cn \
--cc=arunr@valvesoftware.com \
--cc=hildawu@realtek.com \
--cc=jason_mao@realsil.com.cn \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zoey_zhou@realsil.com.cn \
/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).