Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-1072-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ v1] avdtp: Fix potential incorrect transaction label
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170508482684.21011.9547197241854864913.git-patchwork-notify@kernel.org>
Date: Fri, 12 Jan 2024 18:40:26 +0000
References: <20240111171635.144825-1-xiaokeqinhealth@126.com>
In-Reply-To: <20240111171635.144825-1-xiaokeqinhealth@126.com>
To: Xiao Yao <xiaokeqinhealth@126.com>
Cc: linux-bluetooth@vger.kernel.org, xiaoyao@rock-chips.com

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 12 Jan 2024 01:16:35 +0800 you wrote:
> From: Xiao Yao <xiaoyao@rock-chips.com>
> 
> Currently, AVDTP commands and responses from remote devices are all
> stored in session.in. When one end has an ongoing transaction and
> immediately starting another transaction, it may cause the session.
> in.transaction to be incorrectly modified, so we need session.in_cmd
> and session.in_rsp to be able to handle outstanding requests in each
> direction.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1] avdtp: Fix potential incorrect transaction label
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1f9ff8fb4048

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