From: BajajSarv <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 129b19: org.bluez.Gatt: Add org.bluez.Error.ImproperlyConf...
Date: Mon, 29 Apr 2024 08:07:39 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/c42702-d2a2aa@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 129b19166304d40073a424d8b9ac28d3802b52f7
https://github.com/bluez/bluez/commit/129b19166304d40073a424d8b9ac28d3802b52f7
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-26 (Fri, 26 Apr 2024)
Changed paths:
M doc/org.bluez.GattCharacteristic.rst
M doc/org.bluez.GattDescriptor.rst
Log Message:
-----------
org.bluez.Gatt: Add org.bluez.Error.ImproperlyConfigured error to
WriteValue
Some attributes may require to generate
BT_ERROR_CCC_IMPROPERLY_CONFIGURED when its CCC is not properly
configured so this adds the possibility to generate it by replying with
org.bluez.Error.ImproperlyConfigured error to WriteValue.
Commit: 9b29784717f4682ca527c76c81b5ba92ba00c313
https://github.com/bluez/bluez/commit/9b29784717f4682ca527c76c81b5ba92ba00c313
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-04-26 (Fri, 26 Apr 2024)
Changed paths:
M src/gatt-database.c
Log Message:
-----------
gatt-database: Implement support to org.bluez.Error.ImproperlyConfigured
This implements support for handling when applications reply with
org.bluez.Error.ImproperlyConfigured the code will translate it to
BT_ERROR_CCC_IMPROPERLY_CONFIGURED.
Fixes: https://github.com/bluez/bluez/issues/827
Commit: d2a2aabee646c4e95655bc5dc93c323efa5fc588
https://github.com/bluez/bluez/commit/d2a2aabee646c4e95655bc5dc93c323efa5fc588
Author: Sarveshwar Bajaj <sarveshwar.bajaj@nxp.com>
Date: 2024-04-29 (Mon, 29 Apr 2024)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
Fix null pointer deference in bap_get_ascs()
Ensure that bap and rdb pointers are valid before accessing or
allocating memory for ascs. Added null check to prevent potential
crash
Compare: https://github.com/bluez/bluez/compare/c42702cfc48e...d2a2aabee646
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-04-29 15:07 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/c42702-d2a2aa@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 read-only IMAP folder(s) and NNTP newsgroup(s).