All of lore.kernel.org
 help / color / mirror / Atom feed
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, max.chou@realtek.com,
	alex_lu@realsil.com.cn
Subject: Re: [PATCH 1/2] Bluetooth: btrtl: Firmware format v3 support
Date: Fri, 30 May 2025 07:49:40 +0800	[thread overview]
Message-ID: <202505300705.KsxzVLt6-lkp@intel.com> (raw)
In-Reply-To: <20250529124816.4186320-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 linus/master v6.15 next-20250529]
[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-Firmware-format-v3-support/20250529-205020
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
patch link:    https://lore.kernel.org/r/20250529124816.4186320-2-hildawu%40realtek.com
patch subject: [PATCH 1/2] Bluetooth: btrtl: Firmware format v3 support
config: arm-randconfig-004-20250530 (https://download.01.org/0day-ci/archive/20250530/202505300705.KsxzVLt6-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250530/202505300705.KsxzVLt6-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/202505300705.KsxzVLt6-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/bluetooth/btusb.c:2707:10: error: call to undeclared function 'btrtl_recv_event'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    2707 |                 return btrtl_recv_event(hdev, skb);
         |                        ^
   1 error generated.


vim +/btrtl_recv_event +2707 drivers/bluetooth/btusb.c

  2689	
  2690	static int btusb_recv_event_realtek(struct hci_dev *hdev, struct sk_buff *skb)
  2691	{
  2692		if (skb->data[0] == HCI_VENDOR_PKT && skb->data[2] == RTK_SUB_EVENT_CODE_COREDUMP) {
  2693			struct rtk_dev_coredump_hdr hdr = {
  2694				.code = RTK_DEVCOREDUMP_CODE_MEMDUMP,
  2695			};
  2696	
  2697			bt_dev_dbg(hdev, "RTL: received coredump vendor evt, len %u",
  2698				skb->len);
  2699	
  2700			btusb_rtl_alloc_devcoredump(hdev, &hdr, skb->data, skb->len);
  2701			kfree_skb(skb);
  2702	
  2703			return 0;
  2704		}
  2705	
  2706		if (skb->data[0] == HCI_VENDOR_PKT)
> 2707			return btrtl_recv_event(hdev, skb);
  2708	
  2709		return hci_recv_frame(hdev, skb);
  2710	}
  2711	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-05-29 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 12:48 [PATCH 0/2] Bluetooth: Add support for RTK firmware version 3 and enhanced ACL-based download acceleration Hilda Wu
2025-05-29 12:48 ` [PATCH 1/2] Bluetooth: btrtl: Firmware format v3 support Hilda Wu
2025-05-29 13:26   ` Bluetooth: Add support for RTK firmware version 3 and enhanced ACL-based download acceleration bluez.test.bot
2025-05-29 23:49   ` kernel test robot [this message]
2025-05-29 12:48 ` [PATCH 2/2] Bluetooth: btrtl: Add enhanced download support Hilda Wu
2025-05-30 11:49   ` kernel test robot

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=202505300705.KsxzVLt6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alex_lu@realsil.com.cn \
    --cc=hildawu@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 \
    /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.