From: NJNXP <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 2f52af: btdev: Fix build error
Date: Tue, 13 Jun 2023 14:01:48 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/303088-d2d2d1@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 2f52afa21a26354a540c1a288480511e90567c6f
https://github.com/bluez/bluez/commit/2f52afa21a26354a540c1a288480511e90567c6f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-06-13 (Tue, 13 Jun 2023)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
btdev: Fix build error
This fixes the following build error:
emulator/btdev.c: In function ‘le_cis_estabilished’:
emulator/btdev.c:5947:22: error: ‘cis_idx’ may be used
uninitialized [-Werror=maybe-uninitialized]
5947 | int cig_idx, cis_idx;
| ^~~~~~~
Commit: 0599a7fa9fce1bbd4a543c6f5bb63f911a676872
https://github.com/bluez/bluez/commit/0599a7fa9fce1bbd4a543c6f5bb63f911a676872
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-06-13 (Tue, 13 Jun 2023)
Changed paths:
M mesh/cfgmod-server.c
Log Message:
-----------
mesh: Fix build error
This fixes the following error:
In function ‘get_composition’,
inlined from ‘cfg_srv_pkt’ at mesh/cfgmod-server.c:801:8:
mesh/cfgmod-server.c:758:9: error: ‘comp’ may be used
uninitialized [-Werror=maybe-uninitialized]
758 | memcpy(buf, comp, len);
| ^~~~~~~~~~~~~~~~~~~~~~
mesh/cfgmod-server.c: In function ‘cfg_srv_pkt’:
mesh/cfgmod-server.c:739:24: note: ‘comp’ was declared here
739 | const uint8_t *comp;
| ^~~~
Commit: 0735ca179fdf127b60c4b4ed502d869b6d10899d
https://github.com/bluez/bluez/commit/0735ca179fdf127b60c4b4ed502d869b6d10899d
Author: Nitin Jadhav <nitin.jadhav@nxp.com>
Date: 2023-06-13 (Tue, 13 Jun 2023)
Changed paths:
M lib/uuid.h
Log Message:
-----------
lib/uuid.h: Add VOCS characteristic uuid(s)
Commit: 52a4d79f22c3f71abe5a17e0ce307547094569f1
https://github.com/bluez/bluez/commit/52a4d79f22c3f71abe5a17e0ce307547094569f1
Author: Nitin Jadhav <nitin.jadhav@nxp.com>
Date: 2023-06-13 (Tue, 13 Jun 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp: Add initial code for handling VOCS
Summary:
- This adds implementation for VOCS service and characteristics
- Implementation based on VOCS_v1.0.pdf specification
- Tested using PTS with reference to VOCS.TS.p1.pdf
Commit: d2d2d12f59d65002c4a671a5af1837f295181142
https://github.com/bluez/bluez/commit/d2d2d12f59d65002c4a671a5af1837f295181142
Author: Nitin Jadhav <nitin.jadhav@nxp.com>
Date: 2023-06-13 (Tue, 13 Jun 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp.c: Make VOCS as an included service of VCS
Fixed the following issue observed during PTS testing
- Specified Upper and Lower Limit for Volume offset
- Corrected the number of handles for VOCS
- VOCS is made as included service of VCS
(VOCS is secondary service and VSC is primary service)
Compare: https://github.com/bluez/bluez/compare/3030883005c0...d2d2d12f59d6
reply other threads:[~2023-06-13 21:01 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/303088-d2d2d1@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).