From: kernel test robot <lkp@intel.com>
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-bluetooth@vger.kernel.org,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Subject: [bluetooth-next:master 40/43] drivers/bluetooth/btnxpuart.c:1683:15: error: 'struct hci_dev' has no member named 'cmd_timeout'; did you mean 'cmd_timer'?
Date: Fri, 7 Mar 2025 10:04:26 +0800 [thread overview]
Message-ID: <202503070916.OR4VIRZh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head: 8968f507940cad09c8e2ecc4631f90d62709e17b
commit: b21ae0e8b43797d7c9c3ae1d97a0257686e24005 [40/43] Bluetooth: btnxpuart: Add support for HCI coredump feature
config: sh-randconfig-002-20250307 (https://download.01.org/0day-ci/archive/20250307/202503070916.OR4VIRZh-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503070916.OR4VIRZh-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/202503070916.OR4VIRZh-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/bluetooth/btnxpuart.c: In function 'nxp_serdev_probe':
>> drivers/bluetooth/btnxpuart.c:1683:15: error: 'struct hci_dev' has no member named 'cmd_timeout'; did you mean 'cmd_timer'?
1683 | hdev->cmd_timeout = nxp_cmd_timeout;
| ^~~~~~~~~~~
| cmd_timer
vim +1683 drivers/bluetooth/btnxpuart.c
1629
1630 static int nxp_serdev_probe(struct serdev_device *serdev)
1631 {
1632 struct hci_dev *hdev;
1633 struct btnxpuart_dev *nxpdev;
1634
1635 nxpdev = devm_kzalloc(&serdev->dev, sizeof(*nxpdev), GFP_KERNEL);
1636 if (!nxpdev)
1637 return -ENOMEM;
1638
1639 nxpdev->nxp_data = (struct btnxpuart_data *)device_get_match_data(&serdev->dev);
1640
1641 nxpdev->serdev = serdev;
1642 serdev_device_set_drvdata(serdev, nxpdev);
1643
1644 serdev_device_set_client_ops(serdev, &btnxpuart_client_ops);
1645
1646 INIT_WORK(&nxpdev->tx_work, btnxpuart_tx_work);
1647 skb_queue_head_init(&nxpdev->txq);
1648
1649 init_waitqueue_head(&nxpdev->fw_dnld_done_wait_q);
1650 init_waitqueue_head(&nxpdev->check_boot_sign_wait_q);
1651
1652 device_property_read_u32(&nxpdev->serdev->dev, "fw-init-baudrate",
1653 &nxpdev->fw_init_baudrate);
1654 if (!nxpdev->fw_init_baudrate)
1655 nxpdev->fw_init_baudrate = FW_INIT_BAUDRATE;
1656
1657 set_bit(BTNXPUART_FW_DOWNLOADING, &nxpdev->tx_state);
1658
1659 crc8_populate_msb(crc8_table, POLYNOMIAL8);
1660
1661 /* Initialize and register HCI device */
1662 hdev = hci_alloc_dev();
1663 if (!hdev) {
1664 dev_err(&serdev->dev, "Can't allocate HCI device\n");
1665 return -ENOMEM;
1666 }
1667
1668 nxpdev->hdev = hdev;
1669
1670 hdev->bus = HCI_UART;
1671 hci_set_drvdata(hdev, nxpdev);
1672
1673 hdev->manufacturer = MANUFACTURER_NXP;
1674 hdev->open = btnxpuart_open;
1675 hdev->close = btnxpuart_close;
1676 hdev->flush = btnxpuart_flush;
1677 hdev->setup = nxp_setup;
1678 hdev->post_init = nxp_post_init;
1679 hdev->send = nxp_enqueue;
1680 hdev->hw_error = nxp_hw_err;
1681 hdev->shutdown = nxp_shutdown;
1682 hdev->wakeup = nxp_wakeup;
> 1683 hdev->cmd_timeout = nxp_cmd_timeout;
1684 SET_HCIDEV_DEV(hdev, &serdev->dev);
1685
1686 if (hci_register_dev(hdev) < 0) {
1687 dev_err(&serdev->dev, "Can't register HCI device\n");
1688 goto probe_fail;
1689 }
1690
1691 if (ps_setup(hdev))
1692 goto probe_fail;
1693
1694 hci_devcd_register(hdev, nxp_coredump, nxp_coredump_hdr, NULL);
1695
1696 return 0;
1697
1698 probe_fail:
1699 hci_free_dev(hdev);
1700 return -ENODEV;
1701 }
1702
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-07 2:04 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=202503070916.OR4VIRZh-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=neeraj.sanjaykale@nxp.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.