From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/3] emulator: bthost: add function for sending raw L2CAP sig commands
Date: Mon, 31 Aug 2026 17:30:08 +0000 [thread overview]
Message-ID: <178819740813.676143.7012117251766286263.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <66d2971217dc632b10049fef7a5e9e735715bca2.1788119838.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 30 Aug 2026 22:57:22 +0300 you wrote:
> Add bthost_l2cap_sig_raw() that tests can use to send raw L2CAP
> signaling commands.
> ---
>
> Notes:
> v2:
> - no changes
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] emulator: bthost: add function for sending raw L2CAP sig commands
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d52d9a173a5f
- [BlueZ,v2,2/3] tools/l2cap-server: add test for invalid Conn Req on Ext-Flowctl server
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3a2d543c4c21
- [BlueZ,v2,3/3] tools/l2cap-tester: test closing sockets with ECRED defer
(no matching commit)
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:[~2026-08-31 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 19:57 [PATCH BlueZ v2 1/3] emulator: bthost: add function for sending raw L2CAP sig commands Pauli Virtanen
2026-08-30 19:57 ` [PATCH BlueZ v2 2/3] tools/l2cap-server: add test for invalid Conn Req on Ext-Flowctl server Pauli Virtanen
2026-08-30 19:57 ` [PATCH BlueZ v2 3/3] tools/l2cap-tester: test closing sockets with ECRED defer Pauli Virtanen
2026-08-30 21:59 ` [BlueZ,v2,1/3] emulator: bthost: add function for sending raw L2CAP sig commands bluez.test.bot
2026-08-31 17:30 ` 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=178819740813.676143.7012117251766286263.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.