From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/3] l2cap-tester: Add tests for multiple data packets
Date: Thu, 27 Jun 2024 18:40:30 +0000 [thread overview]
Message-ID: <171951363053.21304.7859779660797220564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240626150229.103047-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 26 Jun 2024 11:02:27 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds the following tests which cover the TX/RX of multiple
> packets (up to 32K):
>
> L2CAP BR/EDR Client - Read 32k Success
> L2CAP BR/EDR Client - Write 32k Success
> L2CAP BR/EDR Server - Read 32k Success
> L2CAP BR/EDR Server - Write 32k Success
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/3] l2cap-tester: Add tests for multiple data packets
(no matching commit)
- [BlueZ,v1,2/3] bthost: Introduce bthost_add_l2cap_server_custom
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b6f8c0024a87
- [BlueZ,v1,3/3] l2cap-tester: Add tests for multiple data packets over LE
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=72c3f5bf1ce6
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:[~2024-06-27 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:02 [PATCH BlueZ v1 1/3] l2cap-tester: Add tests for multiple data packets Luiz Augusto von Dentz
2024-06-26 15:02 ` [PATCH BlueZ v1 2/3] bthost: Introduce bthost_add_l2cap_server_custom Luiz Augusto von Dentz
2024-06-26 15:02 ` [PATCH BlueZ v1 3/3] l2cap-tester: Add tests for multiple data packets over LE Luiz Augusto von Dentz
2024-06-26 17:39 ` [BlueZ,v1,1/3] l2cap-tester: Add tests for multiple data packets bluez.test.bot
2024-06-27 18:40 ` 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=171951363053.21304.7859779660797220564.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 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.