From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 790a0c: bap: Do not clear user_data before detaching bt_bap
Date: Fri, 21 Feb 2025 08:41:26 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/65fbc4-fc7be1@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 790a0c5d75ec98697edd5173236da49544cefc3e
https://github.com/bluez/bluez/commit/790a0c5d75ec98697edd5173236da49544cefc3e
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Do not clear user_data before detaching bt_bap
After detaching a bt_bap session, each plugin that registered a bap
detached callback will be notified. The bt_bap user data should be
set when calling these callbacks, so the bt_bap session can be
matched to the associated service and the cleanup is handled
accordingly.
Commit: cfb233b4c6b3020627014a4fffbfe16e2db8e891
https://github.com/bluez/bluez/commit/cfb233b4c6b3020627014a4fffbfe16e2db8e891
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Do not set adapter as bt_bap user_data
In case of a BAP Broadcast Source session, it is not necessary to set the
adapter as bt_bap user data. Plus, setting it makes it confusing for
plugins to know the type of pointer to parse, distinguishing between
Broadcast Source sessions and other types of sessions that hold a service
reference as user data.
For a BAP Broadcast Source, the bt_bap user data can remain unset, since
the session is not associated with any remote device/service.
Commit: fefeb495dd227c7fb13d68cafe641183fdd05d47
https://github.com/bluez/bluez/commit/fefeb495dd227c7fb13d68cafe641183fdd05d47
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
bass: Add checks for bap user data
This adds checks before parsing bt_bap user data in bap attached/detached,
to avoid accessing NULL pointers in case the user data has been cleared
or has not been set before attaching a BAP session.
Commit: 1c4f5276723627a5844c92f8f23bfa552145939a
https://github.com/bluez/bluez/commit/1c4f5276723627a5844c92f8f23bfa552145939a
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M obexd/client/map.c
Log Message:
-----------
obexd/client/map: Add SupportedTypes property to MessageAccess1
This lists the message types supported the remote MSE.
Possible values are: EMAIL, SMS_GSM, SMS_CDMA, MMS and IM.
Those values can be used as message type when sending a message
using PushMessage method.
Commit: 41431caf8af3399385b27115977124847ae76489
https://github.com/bluez/bluez/commit/41431caf8af3399385b27115977124847ae76489
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M doc/org.bluez.obex.MessageAccess.rst
Log Message:
-----------
doc: Add SupportedTypes property to MessageAccess1
Commit: fc7be1e8677158796c321d03618df13cdca270b4
https://github.com/bluez/bluez/commit/fc7be1e8677158796c321d03618df13cdca270b4
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M tools/avtest.c
Log Message:
-----------
tools/avtest: Add AAC configuration
The tests A2DP/SNK/AVP/BI-01-C, A2DP/SNK/AVP/BI-02-C,
A2DP/SNK/AVP/BI-05-C and A2DP/SNK/AVP/BI-07-C expect the IUT to
provide an AAC configuration.
This can be used by adding '--aac' to the avtest command, e.g. for
A2DP/SNK/AVP/BI-01-C test:
tools/avtest --aac --reject setconf --reject-code 214
Compare: https://github.com/bluez/bluez/compare/65fbc47143a5...fc7be1e86771
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-02-21 16:41 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/65fbc4-fc7be1@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.