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, quic_saluvala@quicinc.com,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: qca: Fix wrong event type for patch config command
Date: Thu, 25 Jan 2024 20:50:25 +0000 [thread overview]
Message-ID: <170621582581.16174.72441742691687427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1705657530-17975-1-git-send-email-quic_zijuhu@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 19 Jan 2024 17:45:30 +0800 you wrote:
> Vendor-specific command patch config has HCI_Command_Complete event as
> response, but qca_send_patch_config_cmd() wrongly expects vendor-specific
> event for the command, fixed by using right event type.
>
> Btmon log for the vendor-specific command are shown below:
> < HCI Command: Vendor (0x3f|0x0000) plen 5
> 28 01 00 00 00
> > HCI Event: Command Complete (0x0e) plen 5
> Vendor (0x3f|0x0000) ncmd 1
> Status: Success (0x00)
> 28
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: qca: Fix wrong event type for patch config command
https://git.kernel.org/bluetooth/bluetooth-next/c/64692e12507b
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:[~2024-01-25 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:45 [PATCH v1] Bluetooth: qca: Fix wrong event type for patch config command Zijun Hu
2024-01-19 10:33 ` [v1] " bluez.test.bot
2024-01-25 20:50 ` 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=170621582581.16174.72441742691687427.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_saluvala@quicinc.com \
--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.