From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 8f0aa4: tools: add 6lowpan-tester
Date: Mon, 13 Oct 2025 11:53:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/9e76fb-2db2d3@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 8f0aa430bfb939cad6dff17c91fac7f8bf3ebec2
https://github.com/bluez/bluez/commit/8f0aa430bfb939cad6dff17c91fac7f8bf3ebec2
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-10-13 (Mon, 13 Oct 2025)
Changed paths:
M Makefile.tools
A tools/6lowpan-tester.c
Log Message:
-----------
tools: add 6lowpan-tester
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
Commit: 2db2d35937997d6098fa89bd1945206a0d23beb8
https://github.com/bluez/bluez/commit/2db2d35937997d6098fa89bd1945206a0d23beb8
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-10-13 (Mon, 13 Oct 2025)
Changed paths:
M doc/test-runner.rst
M doc/tester.config
Log Message:
-----------
doc: enable 6lowpan in tester.config and explain in test-runner.rst
Now that there is a 6lowpan-tester, enable requirements in tester
config, and explain what is needed in test-runner.rst
Compare: https://github.com/bluez/bluez/compare/9e76fb9f6ce8...2db2d3593799
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-13 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/9e76fb-2db2d3@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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