From: Arkadiusz Bokowy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] be79cd: shared/bap: Fix not updating location
Date: Fri, 12 Apr 2024 08:19:56 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/fe71fa-6b5447@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: be79cd19c5c5f6b42e40c0edb04d67ab21773f19
https://github.com/bluez/bluez/commit/be79cd19c5c5f6b42e40c0edb04d67ab21773f19
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-11 (Thu, 11 Apr 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Fix not updating location
Fix not updating map.location when selecting.
Commit: c7dcd064057fb89628c5da55da91dff363b559ca
https://github.com/bluez/bluez/commit/c7dcd064057fb89628c5da55da91dff363b559ca
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-11 (Thu, 11 Apr 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Make bt_bap_select fallback in case of no channel allocation
If channel allocation could not be matched attempt to call .select
without a channel allocation as the device might require a different
matching algorithm.
Fixes: https://github.com/bluez/bluez/issues/793
Commit: 7db85520b76d4acdcea1301dcf80a4ca5f228e1b
https://github.com/bluez/bluez/commit/7db85520b76d4acdcea1301dcf80a4ca5f228e1b
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-11 (Thu, 11 Apr 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Fix not resuming reading attributes
If there is an unexpected disconnect and some attributes values
where left uninitialized this attempts to resume reading them once a
new session is attached.
Commit: 9be5d8018dd1b75cb9cf9d206b389049a0515c74
https://github.com/bluez/bluez/commit/9be5d8018dd1b75cb9cf9d206b389049a0515c74
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-11 (Thu, 11 Apr 2024)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Update properties of endpoints
If a MediaEndpoint if found during registration stage attempt to check
and update properties since they may have been updated at later stage
when a session has been attached.
Commit: 6b544758375c3c68c92cec1e32c83a8ba24e4e59
https://github.com/bluez/bluez/commit/6b544758375c3c68c92cec1e32c83a8ba24e4e59
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2024-04-12 (Fri, 12 Apr 2024)
Changed paths:
M src/advertising.c
Log Message:
-----------
advertising: Do not crash in case of adv update failure
The refresh_extended_adv() is used in case of direct advertising
request from the client or in case of advertising properties update
or configured advertising timeout. In the two latter cases it is not
possible to prepare reply D-Bus message, because there is no request
message to begin with.
bluetoothd: ../src/advertising.c:add_client_complete() Failed to add
advertisement: Busy (0x0a)
dbus: arguments to dbus_message_get_no_reply() were incorrect, assertion
"message != NULL" failed in file ../../../dbus/dbus-message.c line 3235.
This is normally a bug in some application using the D-Bus library.
Compare: https://github.com/bluez/bluez/compare/fe71fa3dfe26...6b544758375c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-04-12 15:19 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/fe71fa-6b5447@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.