From: kernel test robot <lkp@intel.com>
To: Jing Cai <jing.cai@mediatek.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Chris Lu <chris.lu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>
Subject: [linux-next:master 12628/12815] drivers/bluetooth/btmtk.c:386:44: error: 'struct hci_dev' has no member named 'dump'
Date: Fri, 30 Jun 2023 17:41:16 +0800 [thread overview]
Message-ID: <202306301756.x8dgyYnL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6352a698ca5bf26a9199202666b16cf741f579f6
commit: 872f8c253cb9e84cb3e7f381dd81c7791c64a05a [12628/12815] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
config: i386-randconfig-i006-20230629 (https://download.01.org/0day-ci/archive/20230630/202306301756.x8dgyYnL-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230630/202306301756.x8dgyYnL-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/202306301756.x8dgyYnL-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/bluetooth/btmtk.c: In function 'btmtk_process_coredump':
>> drivers/bluetooth/btmtk.c:386:44: error: 'struct hci_dev' has no member named 'dump'
386 | schedule_delayed_work(&hdev->dump.dump_timeout,
| ^~
vim +386 drivers/bluetooth/btmtk.c
369
370 int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
371 {
372 struct btmediatek_data *data = hci_get_priv(hdev);
373 int err;
374
375 if (!IS_ENABLED(CONFIG_DEV_COREDUMP))
376 return 0;
377
378 switch (data->cd_info.state) {
379 case HCI_DEVCOREDUMP_IDLE:
380 err = hci_devcd_init(hdev, MTK_COREDUMP_SIZE);
381 if (err < 0)
382 break;
383 data->cd_info.cnt = 0;
384
385 /* It is supposed coredump can be done within 5 seconds */
> 386 schedule_delayed_work(&hdev->dump.dump_timeout,
387 msecs_to_jiffies(5000));
388 fallthrough;
389 case HCI_DEVCOREDUMP_ACTIVE:
390 default:
391 err = hci_devcd_append(hdev, skb);
392 if (err < 0)
393 break;
394 data->cd_info.cnt++;
395
396 /* Mediatek coredump data would be more than MTK_COREDUMP_NUM */
397 if (data->cd_info.cnt > MTK_COREDUMP_NUM &&
398 skb->len > sizeof(MTK_COREDUMP_END) &&
399 !memcmp((char *)&skb->data[skb->len - sizeof(MTK_COREDUMP_END)],
400 MTK_COREDUMP_END, sizeof(MTK_COREDUMP_END) - 1)) {
401 bt_dev_info(hdev, "Mediatek coredump end");
402 hci_devcd_complete(hdev);
403 }
404
405 break;
406 }
407
408 if (err < 0)
409 kfree_skb(skb);
410
411 return err;
412 }
413 EXPORT_SYMBOL_GPL(btmtk_process_coredump);
414
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-30 9:41 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=202306301756.x8dgyYnL-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.lu@mediatek.com \
--cc=jing.cai@mediatek.com \
--cc=linux-mm@kvack.org \
--cc=luiz.von.dentz@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sean.wang@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;
as well as URLs for NNTP newsgroup(s).