[PATCH 1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()

[patchwork-bot+bluetooth at kernel.org]

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz at intel.com>:

On Wed, 15 Jan 2025 19:36:36 -0800 you wrote:
> The documentation for usb_driver_claim_interface() says that "the
> device lock" is needed when the function is called from places other
> than probe(). This appears to be the lock for the USB interface
> device. The Mediatek btusb code gets called via this path:
> 
>   Workqueue: hci0 hci_power_on [bluetooth]
>   Call trace:
>    usb_driver_claim_interface
>    btusb_mtk_claim_iso_intf
>    btusb_mtk_setup
>    hci_dev_open_sync
>    hci_power_on
>    process_scheduled_works
>    worker_thread
>    kthread
> 
> [...]

Here is the summary with links:
  - [1/2] Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()
    https://git.kernel.org/bluetooth/bluetooth-next/c/ec5570088c6a
  - [2/2] Bluetooth: btusb: mediatek: Add err code to btusb claim iso printout
    https://git.kernel.org/bluetooth/bluetooth-next/c/6ca1c15fcb92

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html