From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: L2CAP: Fix not tracking outstanding TX ident
Date: Mon, 26 Jan 2026 21:20:04 +0000 [thread overview]
Message-ID: <176946240461.182938.11009851765941243105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260126175340.3576865-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 Mon, 26 Jan 2026 12:53:40 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This attempts to proper track outstanding request by using struct ida
> and allocating from it in l2cap_get_ident using ida_alloc_range which
> would reuse ids as they are free, then upon completion release
> the id using ida_free.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: L2CAP: Fix not tracking outstanding TX ident
https://git.kernel.org/bluetooth/bluetooth-next/c/8e7c7cb168a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-26 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 17:53 [PATCH v3] Bluetooth: L2CAP: Fix not tracking outstanding TX ident Luiz Augusto von Dentz
2026-01-26 18:50 ` [v3] " bluez.test.bot
2026-01-26 21:20 ` patchwork-bot+bluetooth [this message]
2026-01-26 22:22 ` [PATCH v3] " Paul Menzel
2026-03-01 23:36 ` Joan Bruguera Micó
2026-03-02 8:27 ` Linux regression tracking (Thorsten Leemhuis)
2026-03-02 14:27 ` Luiz Augusto von Dentz
2026-03-15 19:43 ` Joan Bruguera Micó
2026-03-16 13:37 ` Luiz Augusto von Dentz
2026-03-17 14:17 ` Thorsten Leemhuis
2026-03-17 15:12 ` Luiz Augusto von Dentz
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=176946240461.182938.11009851765941243105.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