From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, brian.gix@intel.com
Subject: [PATCH BlueZ v4 0/2] Add mesh testing support
Date: Wed, 31 Aug 2022 16:59:30 -0700 [thread overview]
Message-ID: <20220831235932.290032-1-brian.gix@intel.com> (raw)
This patch set reserves MGMT events and opcodes for Mesh, and adds a new
unit tester for those features: mesh-tester
v2 - v4: Fix whitespace
Brian Gix (2):
lib: Add mgmt opcodes and events for Mesh
tools: Add mesh-tester to test Kernel mesh support
Makefile.tools | 12 +-
lib/mgmt.h | 47 ++
tools/mesh-tester.c | 1441 +++++++++++++++++++++++++++++++++++++++++++
tools/test-runner.c | 2 +
4 files changed, 1501 insertions(+), 1 deletion(-)
create mode 100644 tools/mesh-tester.c
--
2.37.2
next reply other threads:[~2022-08-31 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 23:59 Brian Gix [this message]
2022-08-31 23:59 ` [PATCH BlueZ v4 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-09-01 3:27 ` Add mesh testing support bluez.test.bot
2022-08-31 23:59 ` [PATCH BlueZ v4 2/2] tools: Add mesh-tester to test Kernel mesh support Brian Gix
2022-09-01 22:00 ` [PATCH BlueZ v4 0/2] Add mesh testing support patchwork-bot+bluetooth
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=20220831235932.290032-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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