From: Christian Eggers <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] f40c58: src/shared: Make default length handle EA
Date: Thu, 02 May 2024 07:32:56 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/6fc599-14057f@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: f40c5857d70a91e417e22da9da20f4193414b8a3
https://github.com/bluez/bluez/commit/f40c5857d70a91e417e22da9da20f4193414b8a3
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-05-02 (Thu, 02 May 2024)
Changed paths:
M src/shared/ad.c
M src/shared/ad.h
Log Message:
-----------
src/shared: Make default length handle EA
By default bt_ad was setting just BT_AD_MAX_DATA_LEN (31) which is not
enough to handle devices advertising using EA, so this switches the
default to be BT_EA_MAX_DATA_LEN (251) since EA is much more common
nowadays and for those case where the it is not supported (e.g. for
advertisers without EA support) then shall be using bt_ad_set_max_len
to adjust the maximum length.
Fixes: https://github.com/bluez/bluez/issues/832
Commit: 14057f2cc0ea31b0f332e65dcfba2197b1e280f2
https://github.com/bluez/bluez/commit/14057f2cc0ea31b0f332e65dcfba2197b1e280f2
Author: Christian Eggers <ceggers@arri.de>
Date: 2024-05-02 (Thu, 02 May 2024)
Changed paths:
M client/gatt.c
Log Message:
-----------
client/gatt: gatt_register_app: fix parsing of UUIDs
- argv[0] (shell command) must not be used as UUID argument
- fixed linked list iteration
Compare: https://github.com/bluez/bluez/compare/6fc599e334ce...14057f2cc0ea
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-05-02 14:32 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/6fc599-14057f@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).