Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-1387-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v1] Bluetooth: qca: Fix wrong event type for patch config
 command
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170621582581.16174.72441742691687427.git-patchwork-notify@kernel.org>
Date: Thu, 25 Jan 2024 20:50:25 +0000
References: <1705657530-17975-1-git-send-email-quic_zijuhu@quicinc.com>
In-Reply-To: <1705657530-17975-1-git-send-email-quic_zijuhu@quicinc.com>
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

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