From: Arkadiusz Bokowy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 8f32fa: battery: Check interface before getting property
Date: Wed, 07 Jun 2023 13:01:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/52477e-08d627@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 8f32fa24cc9d044263bef468ef940d4353456f31
https://github.com/bluez/bluez/commit/8f32fa24cc9d044263bef468ef940d4353456f31
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2023-06-06 (Tue, 06 Jun 2023)
Changed paths:
M src/battery.c
Log Message:
-----------
battery: Check interface before getting property
Client can export other interfaces than the BatteryProvide1 on the
registered object manager. So, before getting battery provider specific
property, validate that we are operating on the right interface.
This change will allow client to implement only one object manger for
media applications, players and battery providers without triggering
error message.
Commit: 08d62744ce179137987154e526e27296cdb1d345
https://github.com/bluez/bluez/commit/08d62744ce179137987154e526e27296cdb1d345
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2023-06-06 (Tue, 06 Jun 2023)
Changed paths:
M profiles/audio/media.c
Log Message:
-----------
media: Register app objects in proxy_added_cb()
The proxy_added_cb() function is called every time a new client is added
to the application object manager. Registering media endpoint and player
in that proxy_added_cb() callback function will allow to register new
endpoints and players not only during the initial RegisterApplication
call, but also during the application lifetime. For instance, this might
allow to dynamically enable/disable support for additional codecs.
Compare: https://github.com/bluez/bluez/compare/52477e80fc89...08d62744ce17
reply other threads:[~2023-06-07 20:01 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/52477e-08d627@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;
as well as URLs for NNTP newsgroup(s).