From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 216b17: shared/tester: add ability to shutdown tester IO
Date: Thu, 19 Jun 2025 08:44:40 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/973896/000000-4f4f7d@github.com> (raw)
Branch: refs/heads/973896
Home: https://github.com/bluez/bluez
Commit: 216b1725387562468a071da7f676dc5bd68823b1
https://github.com/bluez/bluez/commit/216b1725387562468a071da7f676dc5bd68823b1
Author: Kirill Samburskiy <k.samburskiy@omp.ru>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M src/shared/tester.c
M src/shared/tester.h
Log Message:
-----------
shared/tester: add ability to shutdown tester IO
Some tests may require the ability to shutdown IO for proper teardown.
Add function tester_shutdown_io to accomplish that.
Commit: 4f4f7dd583ba843392ccb7451e1e2ee3eb4d4c59
https://github.com/bluez/bluez/commit/4f4f7dd583ba843392ccb7451e1e2ee3eb4d4c59
Author: Kirill Samburskiy <k.samburskiy@omp.ru>
Date: 2025-06-19 (Thu, 19 Jun 2025)
Changed paths:
M unit/test-vcp.c
Log Message:
-----------
test-vcp: free server-side bt_vcp on test teardown
Shutdown tester IO before freeing bt_att instance to trigger its IO
disconnection callbacks. This detaches bt_vcp instance created by
vcp_get_session function, and executes detach callback registered
through bt_vcp_register that frees memory used by this bt_vcp instance.
This prevents the test from failing in some environments.
Compare: https://github.com/bluez/bluez/compare/216b17253875%5E...4f4f7dd583ba
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-19 15:44 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/973896/000000-4f4f7d@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 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.