[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171741963017.17349.14932650657966489507.git-patchwork-notify@kernel.org>
Date: Mon, 03 Jun 2024 13:00:30 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Ying Hsu <yinghsu@...omium.org>
Cc: linux-bluetooth@...r.kernel.org, luiz.dentz@...il.com,
pmenzel@...gen.mpg.de, horms@...nel.org,
chromeos-bluetooth-upstreaming@...omium.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, johan.hedberg@...il.com,
marcel@...tmann.org, pabeni@...hat.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v4] Bluetooth: Add vendor-specific packet classification for
ISO data
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
On Wed, 29 May 2024 08:00:00 +0000 you wrote:
> When HCI raw sockets are opened, the Bluetooth kernel module doesn't
> track CIS/BIS connections. User-space applications have to identify
> ISO data by maintaining connection information and look up the mapping
> for each ACL data packet received. Besides, btsnoop log captured in
> kernel couldn't tell ISO data from ACL data in this case.
>
> To avoid additional lookups, this patch introduces vendor-specific
> packet classification for Intel BT controllers to distinguish
> ISO data packets from ACL data packets.
>
> [...]
Here is the summary with links:
- [v4] Bluetooth: Add vendor-specific packet classification for ISO data
https://git.kernel.org/bluetooth/bluetooth-next/c/d33224ba26e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists