From: patchwork-bot+bluetooth@kernel.org
To: Mahesh Talewad <mahesh.talewad@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
devyani.godbole@nxp.com, nitin.jadhav@nxp.com
Subject: Re: [PATCH BlueZ v1 0/2] Implementation of AICS
Date: Mon, 18 Dec 2023 20:50:24 +0000 [thread overview]
Message-ID: <170293262406.10818.9217822891982559355.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231129134058.70612-1-mahesh.talewad@nxp.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 29 Nov 2023 15:40:56 +0200 you wrote:
> Hello Maintainers,
>
> This Patch contains code for implementation of Service - AICS.
> - This code covers all mandatory features of AICS.
> - Verification: All mandatory PTS testcases of AICS are passed.
> - Specification referred for implementation:
> AICS_v1.0.pdf
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] - Added AICS Characteristics UUID(s).
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c89ebba80f27
- [BlueZ,v1,2/2] - Code Implementation related Service- AICS. - Specification referred for implementation: AICS_v1.0.pdf - Verification: Tested all Mandatory PTS testcases and all mandatory testcases passed.
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-18 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 13:40 [PATCH BlueZ v1 0/2] Implementation of AICS Mahesh Talewad
2023-11-29 13:40 ` [PATCH BlueZ v1 1/2] - Added AICS Characteristics UUID(s) Mahesh Talewad
2023-11-29 15:09 ` Implementation of AICS bluez.test.bot
2023-11-29 13:40 ` [PATCH BlueZ v1 2/2] - Code Implementation related Service- AICS. - Specification referred for implementation: AICS_v1.0.pdf - Verification: Tested all Mandatory PTS testcases and all mandatory testcases passed Mahesh Talewad
2023-12-18 20:50 ` patchwork-bot+bluetooth [this message]
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=170293262406.10818.9217822891982559355.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devyani.godbole@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mahesh.talewad@nxp.com \
--cc=nitin.jadhav@nxp.com \
/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.