From: "Jonas Dreßler" <verdre@v0yd.nl>
To: linux-bluetooth@vger.kernel.org,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Jonas Dreßler" <verdre@v0yd.nl>
Subject: [PATCH BlueZ 0/4] Adjust tests for sequential conn establishing
Date: Mon, 29 Jan 2024 12:48:56 +0100 [thread overview]
Message-ID: <20240129114900.92919-1-verdre@v0yd.nl> (raw)
We're going to change the logic to establish connections to ACL
devices in the kernel so that they only happen sequentially,
similar to what we're already doing for "LE Create Connection".
This needs a change in mgmt-tester, and while at it, let's also
introduce a test verifying the new behavior.
Also included in this series is a small drive-by fix for running
mgmt-tester with address sanititzer.
Kernel series: https://lore.kernel.org/linux-bluetooth/20240108224614.56900-1-verdre@v0yd.nl/
Jonas Dreßler (4):
mgmt-tester: Add a 0-opcode to expect_hci_list lists
mgmt-tester: Adjust a test for recent kernel changes
emulator/btdev: Send page timeout after 2 secs delay
mgmt-tester: Add a test for connecting sequentially
emulator/btdev.c | 30 ++++++++++-
tools/mgmt-tester.c | 129 +++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 157 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-29 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:48 Jonas Dreßler [this message]
2024-01-29 11:48 ` [PATCH BlueZ 1/4] mgmt-tester: Add a 0-opcode to expect_hci_list lists Jonas Dreßler
2024-01-29 13:40 ` Luiz Augusto von Dentz
2024-02-06 10:26 ` Jonas Dreßler
2024-01-29 13:52 ` Adjust tests for sequential conn establishing bluez.test.bot
2024-01-29 11:48 ` [PATCH BlueZ 2/4] mgmt-tester: Adjust a test for recent kernel changes Jonas Dreßler
2024-01-29 13:41 ` Luiz Augusto von Dentz
2024-01-29 11:48 ` [PATCH BlueZ 3/4] emulator/btdev: Send page timeout after 2 secs delay Jonas Dreßler
2024-01-29 13:58 ` Luiz Augusto von Dentz
2024-01-29 11:49 ` [PATCH BlueZ 4/4] mgmt-tester: Add a test for connecting sequentially Jonas Dreßler
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=20240129114900.92919-1-verdre@v0yd.nl \
--to=verdre@v0yd.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).