From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] tools: add 6lowpan-tester
Date: Mon, 13 Oct 2025 19:00:08 +0000 [thread overview]
Message-ID: <176038200829.3178322.16746808324448736281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ced3d6d6e7591bbce715a683a3902cc564c6d3fc.1760378120.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 Mon, 13 Oct 2025 20:57:43 +0300 you wrote:
> Add 6lowpan smoke testing. It only exercises the kernel 6lowpan L2CAP
> connection handling, ipv6 testing is mostly out of scope for the tester.
>
> Add tests:
>
> Basic Framework - Success
> Client Connect - Terminate
> Client Connect - Disable
> Client Connect - Disconnect
> Client Recv Dgram - Success
> Client Recv Raw - Success
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] tools: add 6lowpan-tester
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8f0aa430bfb9
- [BlueZ,v2,2/2] doc: enable 6lowpan in tester.config and explain in test-runner.rst
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2db2d3593799
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:[~2025-10-13 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 17:57 [PATCH BlueZ v2 1/2] tools: add 6lowpan-tester Pauli Virtanen
2025-10-13 17:57 ` [PATCH BlueZ v2 2/2] doc: enable 6lowpan in tester.config and explain in test-runner.rst Pauli Virtanen
2025-10-13 19:00 ` patchwork-bot+bluetooth [this message]
2025-10-13 19:43 ` [BlueZ,v2,1/2] tools: add 6lowpan-tester bluez.test.bot
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=176038200829.3178322.16746808324448736281.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox