From: patchwork-bot+bluetooth@kernel.org
To: Ajay KV <ajay.k.v@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.sriv@intel.com,
kiran.k@intel.com
Subject: Re: [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids
Date: Tue, 13 Feb 2024 20:50:28 +0000 [thread overview]
Message-ID: <170785742894.22526.11138711747518901620.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240212161726.3097145-1-ajay.k.v@intel.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 12 Feb 2024 18:17:24 +0200 you wrote:
> ---
> lib/uuid.c | 9 +++++++++
> lib/uuid.h | 1 +
> 2 files changed, 10 insertions(+)
Here is the summary with links:
- [BlueZ,1/3] lib/uuid: Add support to compare 16bit uuids
(no matching commit)
- [BlueZ,2/3] lib/uuid: Add GTBS UUIDS for Call Control Profile.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=24d97e35fcde
- [BlueZ,3/3] shared/ccp: Add initial code for Call Control Profile for Client Role.
(no matching commit)
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: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 16:17 [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids Ajay KV
2024-02-12 12:26 ` [BlueZ,1/3] " bluez.test.bot
2024-02-12 16:17 ` [PATCH BlueZ 2/3] lib/uuid: Add GTBS UUIDS for Call Control Profile Ajay KV
2024-02-12 16:17 ` [PATCH BlueZ 3/3] shared/ccp: Add initial code for Call Control Profile for Client Role Ajay KV
2024-02-12 12:23 ` Paul Menzel
2024-02-12 12:27 ` Paul Menzel
2024-02-13 20:50 ` patchwork-bot+bluetooth [this message]
2024-02-13 21:56 [PATCH BlueZ 1/3] lib/uuid: Add support to compare 16bit uuids 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=170785742894.22526.11138711747518901620.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 \
--cc=ravishankar.sriv@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 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.