From: patchwork-bot+bluetooth@kernel.org
To: Sathish Narasimman <sathish.narasimman@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/4] lib/uuid: Add VCS UUIDs
Date: Thu, 15 Sep 2022 21:20:15 +0000 [thread overview]
Message-ID: <166327681501.24209.16329562314897625508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220915095412.462210-1-sathish.narasimman@intel.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 15 Sep 2022 15:24:09 +0530 you wrote:
> This adds Volume Control Service UUIDs which will be used by
> Volume Control Profile.
> ---
> lib/uuid.h | 7 +++++++
> 1 file changed, 7 insertions(+)
Here is the summary with links:
- [BlueZ,v2,1/4] lib/uuid: Add VCS UUIDs
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=af1bfbb470c0
- [BlueZ,v2,2/4] shared/vcp: Add initial code for handling VCP
(no matching commit)
- [BlueZ,v2,3/4] profiles: Add initial code for vcp plugin
(no matching commit)
- [BlueZ,v2,4/4] monitor/att: Add decoding support for Volume Control Serice
(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:[~2022-09-15 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 9:54 [PATCH BlueZ v2 1/4] lib/uuid: Add VCS UUIDs Sathish Narasimman
2022-09-15 9:54 ` [PATCH BlueZ v2 2/4] shared/vcp: Add initial code for handling VCP Sathish Narasimman
2022-09-15 9:54 ` [PATCH BlueZ v2 3/4] profiles: Add initial code for vcp plugin Sathish Narasimman
2022-09-15 9:54 ` [PATCH BlueZ v2 4/4] monitor/att: Add decoding support for Volume Control Serice Sathish Narasimman
2022-09-15 20:59 ` Luiz Augusto von Dentz
2022-09-15 11:36 ` [BlueZ,v2,1/4] lib/uuid: Add VCS UUIDs bluez.test.bot
2022-09-15 21:00 ` Luiz Augusto von Dentz
2022-09-16 5:02 ` Sathish Narasimman
2022-09-15 21:20 ` 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=166327681501.24209.16329562314897625508.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sathish.narasimman@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox