From: patchwork-bot+bluetooth@kernel.org
To: Ajay KV <ajay.k.v@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: Re: [PATCH v2 2/3] lib/uuid: Add GTBS UUIDs for Call Control Profile
Date: Tue, 13 Feb 2024 20:50:29 +0000 [thread overview]
Message-ID: <170785742901.22526.3965587945275155347.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213215703.21507-5-ajay.k.v@intel.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 13 Feb 2024 23:57:02 +0200 you wrote:
> ---
> lib/uuid.h | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
Here is the summary with links:
- [v2,2/3] lib/uuid: Add GTBS UUIDs for Call Control Profile
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=24d97e35fcde
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-02-13 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 21:56 [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-13 18:01 ` [BlueZ,1/3] " bluez.test.bot
2024-02-13 20:50 ` [PATCH BlueZ 1/3] " patchwork-bot+bluetooth
2024-02-13 21:56 ` [PATCH BlueZ 2/3] lib/uuid: Add GTBS UUIDS for Call Control Profile Ajay KV
2024-02-13 21:57 ` [PATCH BlueZ 3/3] shared/ccp: Add initial code for Call Control Profile for Client Role Ajay KV
2024-02-13 21:57 ` [PATCH v2 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-13 17:34 ` [v2,1/3] " bluez.test.bot
2024-02-13 20:50 ` [PATCH v2 1/3] " patchwork-bot+bluetooth
2024-02-13 21:57 ` [PATCH v2 2/3] lib/uuid: Add GTBS UUIDs for Call Control Profile Ajay KV
2024-02-13 20:50 ` patchwork-bot+bluetooth [this message]
2024-02-13 21:57 ` [PATCH v2 3/3] shared/ccp: Add initial code for Call Control Profile for Client Role Ajay KV
2024-02-13 20:50 ` patchwork-bot+bluetooth
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=170785742901.22526.3965587945275155347.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ajay.k.v@intel.com \
--cc=kiran.k@intel.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).