From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <zijun.hu@oss.qualcomm.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
quic_rjliao@quicinc.com, brgl@kernel.org, ytkim@qca.qualcomm.com,
quic_bgodavar@quicinc.com, mka@chromium.org,
quic_tjiang@quicinc.com, zijun_hu@icloud.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.von.dentz@intel.com, linux-arm-msm@vger.kernel.org,
bartosz.golaszewski@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com
Subject: Re: [PATCH v2 00/12] Bluetooth: btusb/btqca/hci_sync: Clean up btusb and fix several bugs
Date: Tue, 30 Jun 2026 20:32:33 +0000 [thread overview]
Message-ID: <178285155338.267316.7362111098834622157.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260625-bt_bugfix-v2-0-93396a6f7d5e@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 25 Jun 2026 22:19:45 -0700 you wrote:
> This series cleans up btusb in preparation for adding a new chip,
> QCC2072, and fixes several pre-existing bugs found along the way.
>
> Bug fixes:
> - qca_set_bdaddr() waited for HCI_EV_VENDOR, but the controller replies
> with a Command Complete event.
> - btusb_set_bdaddr_wcn6855() sent the BD_ADDR without byte-swapping it.
> - btusb QCA populated devcoredump fields on devices where devcoredump is
> not enabled.
> - BTUSB_IGNORE is a bitmask and must be tested with '&', not '=='.
>
> [...]
Here is the summary with links:
- [v2,01/12] Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event
https://git.kernel.org/bluetooth/bluetooth-next/c/1718f3a121dd
- [v2,02/12] Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855()
https://git.kernel.org/bluetooth/bluetooth-next/c/cb9fed45d399
- [v2,03/12] Bluetooth: btusb: Record matched usb_device_id into btusb_data
https://git.kernel.org/bluetooth/bluetooth-next/c/97138867591e
- [v2,04/12] Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices
https://git.kernel.org/bluetooth/bluetooth-next/c/0a7575521e2e
- [v2,05/12] Bluetooth: btusb: QCA: move qca_dump out of struct btusb_data
https://git.kernel.org/bluetooth/bluetooth-next/c/bafbbfe43876
- [v2,06/12] Bluetooth: hci_sync: Introduce __hci_reset_sync() for device drivers
https://git.kernel.org/bluetooth/bluetooth-next/c/dc4d5e617358
- [v2,07/12] Bluetooth: btqca: Simplify qca_send_reset() by using __hci_reset_sync()
https://git.kernel.org/bluetooth/bluetooth-next/c/6ccd5c9a56dd
- [v2,08/12] Bluetooth: btusb: Simplify btusb_shutdown_qca() by using __hci_reset_sync()
https://git.kernel.org/bluetooth/bluetooth-next/c/738df2031c56
- [v2,09/12] Bluetooth: hci_sync: Simplify hci_reset_sync()
https://git.kernel.org/bluetooth/bluetooth-next/c/a16a8312f80f
- [v2,10/12] Bluetooth: hci_event: Log error for HCI reset status error in hci_cc_reset()
(no matching commit)
- [v2,11/12] Bluetooth: btusb: Reduce a redundant assignment in btusb_probe()
https://git.kernel.org/bluetooth/bluetooth-next/c/37ecdbcfd7cb
- [v2,12/12] Bluetooth: btusb: Use & instead of == to test bitflag BTUSB_IGNORE
https://git.kernel.org/bluetooth/bluetooth-next/c/5d490bc8bda1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-30 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 5:19 [PATCH v2 00/12] Bluetooth: btusb/btqca/hci_sync: Clean up btusb and fix several bugs Zijun Hu
2026-06-26 5:19 ` [PATCH v2 01/12] Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event Zijun Hu
2026-06-26 8:39 ` Bluetooth: btusb/btqca/hci_sync: Clean up btusb and fix several bugs bluez.test.bot
2026-06-26 5:19 ` [PATCH v2 02/12] Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() Zijun Hu
2026-06-26 5:19 ` [PATCH v2 03/12] Bluetooth: btusb: Record matched usb_device_id into btusb_data Zijun Hu
2026-06-26 5:19 ` [PATCH v2 04/12] Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices Zijun Hu
2026-06-26 5:19 ` [PATCH v2 05/12] Bluetooth: btusb: QCA: move qca_dump out of struct btusb_data Zijun Hu
2026-06-26 5:19 ` [PATCH v2 06/12] Bluetooth: hci_sync: Introduce __hci_reset_sync() for device drivers Zijun Hu
2026-06-26 5:19 ` [PATCH v2 07/12] Bluetooth: btqca: Simplify qca_send_reset() by using __hci_reset_sync() Zijun Hu
2026-06-26 5:19 ` [PATCH v2 08/12] Bluetooth: btusb: Simplify btusb_shutdown_qca() " Zijun Hu
2026-06-26 5:19 ` [PATCH v2 09/12] Bluetooth: hci_sync: Simplify hci_reset_sync() Zijun Hu
2026-06-26 5:19 ` [PATCH v2 10/12] Bluetooth: hci_event: Log error for HCI reset status error in hci_cc_reset() Zijun Hu
2026-06-30 14:43 ` Bartosz Golaszewski
2026-06-26 5:19 ` [PATCH v2 11/12] Bluetooth: btusb: Reduce a redundant assignment in btusb_probe() Zijun Hu
2026-06-26 5:19 ` [PATCH v2 12/12] Bluetooth: btusb: Use & instead of == to test bitflag BTUSB_IGNORE Zijun Hu
2026-06-30 20:32 ` patchwork-bot+bluetooth [this message]
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=178285155338.267316.7362111098834622157.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=quic_tjiang@quicinc.com \
--cc=ytkim@qca.qualcomm.com \
--cc=zijun.hu@oss.qualcomm.com \
--cc=zijun_hu@icloud.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 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.