From: Marcel Holtmann <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 95838e: shared/vcp: Fix notification endianness
Date: Fri, 15 Dec 2023 08:39:21 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/477c41-04ecf6@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 95838efc07d34c6ac121c65daa3316bf50f0374f
https://github.com/bluez/bluez/commit/95838efc07d34c6ac121c65daa3316bf50f0374f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp: Fix notification endianness
4db4d5fa1c4f ("shared/vcp: Fix endianness errors") does attempt to fix
the endianness of stored volume offset but in the process it broke the
notification since the value is no longer stored in the Bluetooth byte
order (Little Endian) but instead in the cpu byte order which is then
used in the notification as is, to fix this instead of notifying using
the stored value it now uses a dedicated variable which does use the
value from the request itself.
Commit: fb681e795027edb3e995e2c75657ebab0360a299
https://github.com/bluez/bluez/commit/fb681e795027edb3e995e2c75657ebab0360a299
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M tools/avtest.c
Log Message:
-----------
tools: avtest: Add reject-code option
Some PTS tests like A2DP/SNK/AVP/BI-03-C, A2DP/SNK/AVP/BI-08-C , …
request some specific rejection code to pass.
This commit adds an option to specify the rejection code during
AVDTP_SET_CONFIGURATION rejection.
E.g. "avtest --reject setconf --reject-code 195" to reject setconf with
INVALID_SAMPLING_FREQUENCY code.
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Commit: 87477b7ffefcf3c64c821d9f700664d89aa2c5f7
https://github.com/bluez/bluez/commit/87477b7ffefcf3c64c821d9f700664d89aa2c5f7
Author: Kiran K <kiran.k@intel.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Update Available context for source
Available Context of sink was getting updated instead of source.
Commit: d5536e0cd431e22be9a1132be6d4af2445590633
https://github.com/bluez/bluez/commit/d5536e0cd431e22be9a1132be6d4af2445590633
Author: Xiao Yao <xiaoyao@rock-chips.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: Fix addr_type for smp_irk/ltk_info/link_key
According to BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 3,
Part H, 2.4.24/2.4.25, The LE LTK and BR/EDR link keys can be
converted between each other, so the addr type can be either
BREDR or LE, so fix it.
Commit: ba9fda12d26bf4200339da94bc198c6641f98668
https://github.com/bluez/bluez/commit/ba9fda12d26bf4200339da94bc198c6641f98668
Author: Xiao Yao <xiaoyao@rock-chips.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M src/device.c
Log Message:
-----------
device: Notify when the bdaddr_type changes
This ensures the AddressType reflects the bdaddr_type stored.
Commit: 093d00b47ee4e3544aa80de33e869a8617c4af32
https://github.com/bluez/bluez/commit/093d00b47ee4e3544aa80de33e869a8617c4af32
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-12-11 (Mon, 11 Dec 2023)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Don't attempt to release if old state was releasing
If the old state was releasing there is no reason to call
bt_bap_stream_release yet again when IO could not be created as that
will likely create a loop situation when the remote stack caches the
codec configuration.
Commit: cd00105c5b7383bffd0198059e7b1fee1e2b6c99
https://github.com/bluez/bluez/commit/cd00105c5b7383bffd0198059e7b1fee1e2b6c99
Author: Marcel Holtmann <marcel@holtmann.org>
Date: 2023-12-13 (Wed, 13 Dec 2023)
Changed paths:
M Makefile.am
Log Message:
-----------
build: Update library version
Commit: 04ecf635ffaa2f7f8bca89cec3a0fbdbeb016dc9
https://github.com/bluez/bluez/commit/04ecf635ffaa2f7f8bca89cec3a0fbdbeb016dc9
Author: Marcel Holtmann <marcel@holtmann.org>
Date: 2023-12-13 (Wed, 13 Dec 2023)
Changed paths:
M ChangeLog
M configure.ac
Log Message:
-----------
Release 5.71
Compare: https://github.com/bluez/bluez/compare/477c41c683ea...04ecf635ffaa
reply other threads:[~2023-12-15 16:39 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/477c41-04ecf6@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).