public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 71b5ea: shared/bap: ignore NULL attach/detach callbacks
Date: Fri, 20 Jun 2025 08:18:21 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/ab13c2-a209d6@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 71b5ea9bf3738755bf644d0a21958e54816c54c4
      https://github.com/bluez/bluez/commit/71b5ea9bf3738755bf644d0a21958e54816c54c4
  Author: Kirill Samburskiy <k.samburskiy@omp.ru>
  Date:   2025-06-20 (Fri, 20 Jun 2025)

  Changed paths:
    M src/shared/bap.c

  Log Message:
  -----------
  shared/bap: ignore NULL attach/detach callbacks

Allow registering NULL attach/detach callbacks with bt_bap_register
for cases when one of callbacks is not needed, e.g. in tests.


  Commit: f5a4e95d73fec983d4b9a6058a0a177856c1b0f1
      https://github.com/bluez/bluez/commit/f5a4e95d73fec983d4b9a6058a0a177856c1b0f1
  Author: Kirill Samburskiy <k.samburskiy@omp.ru>
  Date:   2025-06-20 (Fri, 20 Jun 2025)

  Changed paths:
    M unit/test-vcp.c

  Log Message:
  -----------
  test-vcp: remove unnecessary bt_vcp allocation

Do not create bt_vcp in test_server since it is not necessary for this
test. Also register bt_vcp detached callback to unref and free
objects created by vcp_get_session.


  Commit: 659fc8fa7037c18b34f2dd66b9188b98ba55f6e1
      https://github.com/bluez/bluez/commit/659fc8fa7037c18b34f2dd66b9188b98ba55f6e1
  Author: Kirill Samburskiy <k.samburskiy@omp.ru>
  Date:   2025-06-20 (Fri, 20 Jun 2025)

  Changed paths:
    M unit/test-micp.c

  Log Message:
  -----------
  test-micp: remove unnecessary bt_micp allocation

Do not create bt_micp in test_server since it is not necessary for this
test. Also register bt_micp detached callback to unref and free
objects created by micp_get_session.


  Commit: a209d69767db0f62d6fdc86a7f73ee4ec749c37f
      https://github.com/bluez/bluez/commit/a209d69767db0f62d6fdc86a7f73ee4ec749c37f
  Author: Kirill Samburskiy <k.samburskiy@omp.ru>
  Date:   2025-06-20 (Fri, 20 Jun 2025)

  Changed paths:
    M src/shared/tester.c
    M src/shared/tester.h

  Log Message:
  -----------
  shared/tester: shutdown tester IO before test teardown

Some tests may require shutdown of tester IO for proper teardown.
Add function tester_shutdown_io to accomplish that and call it
automatically when test finishes.


Compare: https://github.com/bluez/bluez/compare/ab13c24eab87...a209d69767db

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2025-06-20 15:18 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/ab13c2-a209d6@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