Received-SPF: pass (google.com: domain of linux-kernel+bounces-199163-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v4] Bluetooth: Add vendor-specific packet classification for
 ISO data
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171741963017.17349.14932650657966489507.git-patchwork-notify@kernel.org>
Date: Mon, 03 Jun 2024 13:00:30 +0000
References: <20240529080123.2146946-1-yinghsu@chromium.org>
In-Reply-To: <20240529080123.2146946-1-yinghsu@chromium.org>
To: Ying Hsu <yinghsu@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
 pmenzel@molgen.mpg.de, horms@kernel.org,
 chromeos-bluetooth-upstreaming@chromium.org, davem@davemloft.net,
 edumazet@google.com, kuba@kernel.org, johan.hedberg@gmail.com,
 marcel@holtmann.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
 netdev@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 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