From: kernel test robot <lkp@intel.com>
To: sean.wang@mediatek.com, nbd@nbd.name, lorenzo.bianconi@redhat.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
sean.wang@mediatek.com, Soul.Huang@mediatek.com,
Leon.Yen@mediatek.com, Eric-SY.Chang@mediatek.com,
Deren.Wu@mediatek.com, km.lin@mediatek.com,
jenhao.yang@mediatek.com, robin.chiu@mediatek.com,
Eddie.Chen@mediatek.com, ch.yeh@mediatek.com,
ted.huang@mediatek.com, Stella.Chang@mediatek.com,
Tom.Chou@mediatek.com, steve.lee@mediatek.com, jsiuda@google.com,
arowa@google.org, frankgor@google.com, kuabhs@google.com,
druth@google.com, abhishekpandit@google.com, shawnku@google.com,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Jing Cai <jing.cai@mediatek.com>,
Chris Lu <chris.lu@mediatek.com>
Subject: Re: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
Date: Sat, 24 Jun 2023 12:00:25 +0800 [thread overview]
Message-ID: <202306241129.L50H0ubx-lkp@intel.com> (raw)
In-Reply-To: <ed1d0e9fe7758dac8a05dcff97c7dcb8e9b0be39.1687565769.git.objelf@gmail.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on next-20230623]
[cannot apply to bluetooth/master wireless/main wireless-next/main linus/master v6.4-rc7]
[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/sean-wang-mediatek-com/Bluetooth-btmtk-introduce-btmtk-reset-work/20230624-100756
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
patch link: https://lore.kernel.org/r/ed1d0e9fe7758dac8a05dcff97c7dcb8e9b0be39.1687565769.git.objelf%40gmail.com
patch subject: [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
config: x86_64-buildonly-randconfig-r002-20230622 (https://download.01.org/0day-ci/archive/20230624/202306241129.L50H0ubx-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230624/202306241129.L50H0ubx-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/202306241129.L50H0ubx-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/bluetooth/btmtk.c:381:32: error: no member named 'dump' in 'struct hci_dev'
schedule_delayed_work(&hdev->dump.dump_timeout,
~~~~ ^
1 error generated.
vim +381 drivers/bluetooth/btmtk.c
364
365 int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
366 {
367 struct btmediatek_data *data = hci_get_priv(hdev);
368 int err;
369
370 if (!IS_ENABLED(CONFIG_DEV_COREDUMP))
371 return 0;
372
373 switch (data->cd_info.state) {
374 case HCI_DEVCOREDUMP_IDLE:
375 err = hci_devcd_init(hdev, MTK_COREDUMP_SIZE);
376 if (err < 0)
377 break;
378 data->cd_info.cnt = 0;
379
380 /* It is supposed coredump can be done within 5 seconds */
> 381 schedule_delayed_work(&hdev->dump.dump_timeout,
382 msecs_to_jiffies(5000));
383 fallthrough;
384 case HCI_DEVCOREDUMP_ACTIVE:
385 default:
386 err = hci_devcd_append(hdev, skb);
387 if (err < 0)
388 break;
389 data->cd_info.cnt++;
390
391 /* Mediatek coredump data would be more than MTK_COREDUMP_NUM */
392 if (data->cd_info.cnt > MTK_COREDUMP_NUM &&
393 skb->len > sizeof(MTK_COREDUMP_END) &&
394 !memcmp((char *)&skb->data[skb->len - sizeof(MTK_COREDUMP_END)],
395 MTK_COREDUMP_END, sizeof(MTK_COREDUMP_END) - 1)) {
396 bt_dev_info(hdev, "Mediatek coredump end");
397 hci_devcd_complete(hdev);
398 }
399
400 break;
401 }
402
403 if (err < 0)
404 kfree_skb(skb);
405
406 return err;
407 }
408 EXPORT_SYMBOL_GPL(btmtk_process_coredump);
409
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-24 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 2:04 [PATCH v7 1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding sean.wang
2023-06-24 2:04 ` [PATCH v7 2/3] Bluetooth: btmtk: introduce btmtk reset work sean.wang
2023-06-24 2:04 ` [PATCH v7 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support sean.wang
2023-06-24 4:00 ` kernel test robot [this message]
2023-06-24 8:35 ` 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=202306241129.L50H0ubx-lkp@intel.com \
--to=lkp@intel.com \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=abhishekpandit@google.com \
--cc=arowa@google.org \
--cc=ch.yeh@mediatek.com \
--cc=chris.lu@mediatek.com \
--cc=druth@google.com \
--cc=frankgor@google.com \
--cc=jenhao.yang@mediatek.com \
--cc=jing.cai@mediatek.com \
--cc=jsiuda@google.com \
--cc=km.lin@mediatek.com \
--cc=kuabhs@google.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@mediatek.com \
--cc=ted.huang@mediatek.com \
/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