From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type
Date: Thu, 10 Jul 2025 15:09:43 +0000 [thread overview]
Message-ID: <175216018349.1518208.18021776664258298180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250709191333.3374053-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 9 Jul 2025 15:13:33 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Due to what seem to be a bug with variant version returned by some
> firmwares the code may set hdev->classify_pkt_type with
> btintel_classify_pkt_type when in fact the controller doesn't even
> support ISO channels feature but may use the handle range expected from
> a controllers that does causing the packets to be reclassified as ISO
> causing several bugs.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type
https://git.kernel.org/bluetooth/bluetooth-next/c/1eea42b9d33f
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:[~2025-07-10 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 19:13 [PATCH v1] Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type Luiz Augusto von Dentz
2025-07-09 19:57 ` [v1] " bluez.test.bot
2025-07-09 20:05 ` [PATCH v1] " Luiz Augusto von Dentz
[not found] ` <CABtds-0U4mD9kr708UdB+SAHRvBAPYrEaOSCjKkqTDXjJpWOUw@mail.gmail.com>
2025-07-10 13:33 ` Luiz Augusto von Dentz
2025-07-10 14:23 ` Sean Rhodes
2025-07-10 14:32 ` Luiz Augusto von Dentz
2025-07-10 14:33 ` Sean Rhodes
2025-07-10 15:09 ` 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=175216018349.1518208.18021776664258298180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox