From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 269f04: mesh: acceptor: fix endianess issues
Date: Tue, 06 May 2025 07:55:59 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/57df14-313de9@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 269f04cd264bda0353514ab2b39de33dcbf2a77a
https://github.com/bluez/bluez/commit/269f04cd264bda0353514ab2b39de33dcbf2a77a
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M mesh/prov-acceptor.c
Log Message:
-----------
mesh: acceptor: fix endianess issues
Members of 'struct mesh_net_prov_caps' are in Over-the-Air order and
must be converted to host order first.
Fixes: 838ddc931263 ("mesh: provisionee: Check prov start parameters")
Commit: 7ca238921f6b69fbc50b51f73bc023ad4e9c9981
https://github.com/bluez/bluez/commit/7ca238921f6b69fbc50b51f73bc023ad4e9c9981
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M mesh/agent.c
Log Message:
-----------
mesh: agent: add hash calculation of URI
Mesh profile spec, 3.9.2 Unprovisioned Device beacon:
Along with the Unprovisioned Device beacon, the device may also
advertise a separate non-connectable advertising packet with a Uniform
Resource Identifier (URI) data type ...
The remaining implementation of this feature does already exist.
Commit: 24d053c09cb797a35574055bfb4846aceabf98ca
https://github.com/bluez/bluez/commit/24d053c09cb797a35574055bfb4846aceabf98ca
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: remove redundant hexdumps in Mesh Provisioning
Paket data is already dumped in the statement above.
Fixes: ad0cdbc1e943 ("monitor: Add basic decoding for Mesh Provisioning")
Commit: f9c8327e5ed1b0d608a4d5b2905e5cb7337c0938
https://github.com/bluez/bluez/commit/f9c8327e5ed1b0d608a4d5b2905e5cb7337c0938
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tools/mesh/cfgcli.c
Log Message:
-----------
tools/mesh-cfgclient: constify
Commit: 30d2de12868d69cb67835b530ed4a0a51f2a5dd8
https://github.com/bluez/bluez/commit/30d2de12868d69cb67835b530ed4a0a51f2a5dd8
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M doc/org.bluez.Media.rst
Log Message:
-----------
org.bluez.Media: add SupportedFeatures
Add SupportedFeatures property for feature information that applications
cannot find otherwise.
Add feature tx-timestamping. Applications cannot enable it on old BlueZ
versions without that feature, as it requires special handling on BlueZ
side.
Commit: 9ea27141c71fef1ae33ac426bc9245cf2aa267eb
https://github.com/bluez/bluez/commit/9ea27141c71fef1ae33ac426bc9245cf2aa267eb
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M profiles/audio/media.c
Log Message:
-----------
media: implement SupportedFeatures property
Add org.bluez.Media.SupportedFeatures. Add feature tx-timestamping.
Commit: 313de9af36cbbd02d69ba12b8819e28f6a89bbd5
https://github.com/bluez/bluez/commit/313de9af36cbbd02d69ba12b8819e28f6a89bbd5
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-05-06 (Tue, 06 May 2025)
Changed paths:
M src/main.conf
Log Message:
-----------
main.conf: Fix documentation of TemporaryTimeout=0
Setting TemporaryTimeout to 0 never enables temporary_timer which means
device_disappeared will never be called and the device will remain
temporary forever (until the service is restarted).
Fixes: https://github.com/bluez/bluez/issues/1100
Compare: https://github.com/bluez/bluez/compare/57df14b8f8b1...313de9af36cb
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-06 14:56 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/57df14-313de9@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.