From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Bluetooth: Support SCO offload for QCA2066
Date: Fri, 08 Dec 2023 15:10:24 +0000 [thread overview]
Message-ID: <170204822465.3151.16308014426635349043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1702000287-22538-1-git-send-email-quic_zijuhu@quicinc.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 8 Dec 2023 09:51:25 +0800 you wrote:
> This patch series are to support HFP offload for QCA2066.
>
> Changes form V3->V4:
> - Bluetooth: hci_conn:
> - - Move non NULL checking into configure_datapath_sync()
> - Bluetooth: qca:
> - - Optimize commmit messages and comments and function names
>
> [...]
Here is the summary with links:
- [v4,1/2] Bluetooth: hci_conn: Check non NULL function before calling for HFP offload
(no matching commit)
- [v4,2/2] Bluetooth: qca: Support HFP offload for QCA2066
https://git.kernel.org/bluetooth/bluetooth-next/c/3d41844703fe
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:[~2023-12-08 15:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:19 [PATCH v1 0/2] Bluetooth: Support SCO offload for QCA2066 Zijun Hu
2023-11-06 6:19 ` [PATCH v1 1/2] Bluetooth: hci_conn: Check non NULL before calling hdev->get_codec_config_data() Zijun Hu
2023-11-06 7:00 ` Bluetooth: Support SCO offload for QCA2066 bluez.test.bot
2023-11-06 6:19 ` [PATCH v1 2/2] Bluetooth: qca: " Zijun Hu
2023-11-29 7:07 ` [PATCH v2 " Zijun Hu
2023-11-06 16:16 ` [PATCH v1 0/2] Bluetooth: " Luiz Augusto von Dentz
2023-11-07 2:46 ` quic_zijuhu
2023-11-17 16:02 ` Luiz Augusto von Dentz
2023-11-29 3:29 ` quic_zijuhu
2023-12-07 21:59 ` quic_zijuhu
2023-11-29 8:07 ` [PATCH v2 " Zijun Hu
2023-11-29 8:07 ` [PATCH v2 1/2] Bluetooth: hci_conn: Check non NULL before calling hdev->get_codec_config_data() Zijun Hu
2023-11-29 8:35 ` Bluetooth: Support SCO offload for QCA2066 bluez.test.bot
2023-11-29 8:07 ` [PATCH v2 2/2] Bluetooth: qca: " Zijun Hu
2023-11-29 8:18 ` [PATCH v2 0/2] Bluetooth: " Zijun Hu
2023-11-29 8:18 ` [PATCH v2 1/2] Bluetooth: hci_conn: Check non NULL before calling hdev->get_codec_config_data() Zijun Hu
2023-11-29 8:58 ` [v2,1/2] " bluez.test.bot
2023-11-29 8:18 ` [PATCH v2 2/2] Bluetooth: qca: Support SCO offload for QCA2066 Zijun Hu
2023-11-29 8:29 ` [PATCH v3 0/2] Bluetooth: " Zijun Hu
2023-11-29 8:29 ` [PATCH v3 1/2] Bluetooth: hci_conn: Check non NULL before calling hdev->get_codec_config_data() Zijun Hu
2023-11-29 8:57 ` Bluetooth: Support SCO offload for QCA2066 bluez.test.bot
2023-11-29 8:29 ` [PATCH v3 2/2] Bluetooth: qca: " Zijun Hu
2023-12-08 1:51 ` [PATCH v4 0/2] Bluetooth: " Zijun Hu
2023-12-08 1:51 ` [PATCH v4 1/2] Bluetooth: hci_conn: Check non NULL function before calling for HFP offload Zijun Hu
2023-12-08 2:47 ` Bluetooth: Support SCO offload for QCA2066 bluez.test.bot
2023-12-08 1:51 ` [PATCH v4 2/2] Bluetooth: qca: Support HFP " Zijun Hu
2023-12-08 15:10 ` 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=170204822465.3151.16308014426635349043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_zijuhu@quicinc.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.