From: maheshtalewad <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] c89ebb: uuid: Add AICS UUIDs
Date: Mon, 18 Dec 2023 13:12:32 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/e01208-eb07ec@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: c89ebba80f27e412d5222737c32b2ed81a6fc80c
https://github.com/bluez/bluez/commit/c89ebba80f27e412d5222737c32b2ed81a6fc80c
Author: Mahesh Talewad <mahesh.talewad@nxp.com>
Date: 2023-12-18 (Mon, 18 Dec 2023)
Changed paths:
M lib/uuid.h
Log Message:
-----------
uuid: Add AICS UUIDs
This adds AISCS related UUIDs.
Commit: 172948d0d6f6330baedec6276c32b07b2b8b69da
https://github.com/bluez/bluez/commit/172948d0d6f6330baedec6276c32b07b2b8b69da
Author: Mahesh Talewad <mahesh.talewad@nxp.com>
Date: 2023-12-18 (Mon, 18 Dec 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp: Implement AICS service
This implements AICS service as referred in AICS_v1.0.pdf.
Commit: eb07ec1f6ffb57f41edbedaeb0da9eb1bd11be28
https://github.com/bluez/bluez/commit/eb07ec1f6ffb57f41edbedaeb0da9eb1bd11be28
Author: Mahesh Talewad <mahesh.talewad@nxp.com>
Date: 2023-12-18 (Mon, 18 Dec 2023)
Changed paths:
M unit/test-vcp.c
Log Message:
-----------
unit/test-vcp.c: Add AICS unit tests
This implements the following test:
Test Summary
------------
AICS/SR/SGGIT/CHA/BV-01-C Passed
AICS/SR/SGGIT/CHA/BV-02-C Passed
AICS/SR/SGGIT/CHA/BV-03-C Passed
AICS/SR/SGGIT/CHA/BV-04-C Passed
AICS/SR/SGGIT/CHA/BV-05-C Passed
AICS/SR/SGGIT/CHA/BV-06-C Passed
AICS/SR/SGGIT/CP/BI-01-C Passed
AICS/SR/SGGIT/CP/BI-02-C Passed
AICS/SR/CP/BV-01-C Passed
AICS/SR/SPE/BI-01-C Passed
Total: 10, Passed: 10 (100.0%), Failed: 0, Not Run: 0
Compare: https://github.com/bluez/bluez/compare/e01208dac67f...eb07ec1f6ffb
reply other threads:[~2023-12-18 21:12 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/e01208-eb07ec@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).