From: Brian Gix <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 44658f: avdtp: fix possible minor problems
Date: Thu, 30 Jun 2022 13:42:43 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/be7ebf-5351d4@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 44658fccacda3ade0ca2adbb2643b489671fe477
https://github.com/bluez/bluez/commit/44658fccacda3ade0ca2adbb2643b489671fe477
Author: lishengyu <lishengyu@uniontech.com>
Date: 2022-06-30 (Thu, 30 Jun 2022)
Changed paths:
M profiles/audio/avdtp.c
Log Message:
-----------
avdtp: fix possible minor problems
It should always be considered that if send_request fails, sep
should be removed from the list and the requested memory freed;
Commit: 8fc3368db84035bee91ce0bea2f7592343e19f81
https://github.com/bluez/bluez/commit/8fc3368db84035bee91ce0bea2f7592343e19f81
Author: Brian Gix <brian.gix@intel.com>
Date: 2022-06-30 (Thu, 30 Jun 2022)
Changed paths:
M src/adapter.c
Log Message:
-----------
core: make bt_uuid_hash() portable across archs
bt_uuid_t is defined as a byte array, so it can cause alignment errors
on some architectures, when the two 64 bit halves are treated as u64s.
This patch ensures proper alignment across all architectures.
Fixes:
src/adapter.c: In function ‘bt_uuid_hash’:
src/adapter.c:3617:8: error: cast increases required alignment of
target type [-Werror=cast-align]
val = (uint64_t *)&uuid_128.value.u128;
^
cc1: all warnings being treated as errors
Commit: 31690310c096994c553c373ab5464cc39fbfe860
https://github.com/bluez/bluez/commit/31690310c096994c553c373ab5464cc39fbfe860
Author: Brian Gix <brian.gix@intel.com>
Date: 2022-06-30 (Thu, 30 Jun 2022)
Changed paths:
M src/device.c
Log Message:
-----------
core: Fix signed vs unsigned compare
__time_t is not a portable data type, and can cause sign mismatch on
some compares.
Fixes:
CC src/bluetoothd-device.o
src/device.c: In function ‘device_is_name_resolve_allowed’:
src/device.c:4092:17: error: comparison of integer expressions of
different signedness: ‘__time_t’ {aka ‘long int’} and
‘long unsigned int’ [-Werror=sign-compare]
if (now.tv_sec >= device->name_resolve_failed_time +
^~
cc1: all warnings being treated as errors
Commit: 5351d4d86a08fbdc7f537b4662c5a070dbf1d0b4
https://github.com/bluez/bluez/commit/5351d4d86a08fbdc7f537b4662c5a070dbf1d0b4
Author: Brian Gix <brian.gix@intel.com>
Date: 2022-06-30 (Thu, 30 Jun 2022)
Changed paths:
M mesh/mesh-config-json.c
Log Message:
-----------
mesh: Fix snprintf return values not being checked
Some versions of the GCC compiler complain when the return value of
snprintf is not checked. This patch cleans up the Mesh JSON parser.
Compare: https://github.com/bluez/bluez/compare/be7ebf29b370...5351d4d86a08
reply other threads:[~2022-06-30 20:42 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/be7ebf-5351d4@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.