From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e60d07: build: Support libical 4.0
Date: Thu, 04 Jun 2026 12:33:04 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/2a6968-c6bc42@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e60d07255327db3fc4e3a28d7fcc792cd42c34d0
https://github.com/bluez/bluez/commit/e60d07255327db3fc4e3a28d7fcc792cd42c34d0
Author: Funda Wang <fundawang@yeah.net>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M configure.ac
Log Message:
-----------
build: Support libical 4.0
libical 4.0 split off some vcal related functions to a separate shared
library, libicalvcal. As libicalvcal depends on libical itself, first
check for libicalvcal being available, and if it fails, check for
just libical.
Closes: https://github.com/bluez/bluez/issues/2090
Tested-by: Bastien Nocera <hadess@hadess.net>
Commit: 646014a6a246fe99df27da12d2de7bcd2e04d0df
https://github.com/bluez/bluez/commit/646014a6a246fe99df27da12d2de7bcd2e04d0df
Author: Wei Deng <wei.deng@oss.qualcomm.com>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M src/profile.c
Log Message:
-----------
profile: Set L2CAP IMTU for OBEX profile listeners
The default_settings entries for OBEX profiles (OPP, FTP, PBAP, MAS,
MNS) have no imtu field, so ext_start_servers() creates the L2CAP
listening socket without an explicit IMTU. This causes the socket to
advertise the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP,
limiting the peer's outgoing PDU size and degrading Rx throughput.
Add an imtu field to default_settings and set it to 32767 for all
OBEX profiles that use L2CAP. Copy the value in ext_set_defaults()
and apply it to the listening socket via bt_io_set() after
bt_io_listen() succeeds.
Commit: c6bc42d696610bfae4e5dc193e1d39371c6b3e0c
https://github.com/bluez/bluez/commit/c6bc42d696610bfae4e5dc193e1d39371c6b3e0c
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: Fix using case sensitive strncmp for pattern match addresses
When matching discovery filter pattern with addresses shall be
considered case insensitive since its binary format that can be
printed using either upper or lower case for the range a-f/A-F.
Compare: https://github.com/bluez/bluez/compare/2a6968b40378...c6bc42d69661
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-04 19:33 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/2a6968-c6bc42@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