From: patchwork-bot+bluetooth@kernel.org
To: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
quic_anubhavg@quicinc.com
Subject: Re: [PATCH BlueZ v1 0/2] Channel Sounding reflector GATT registration and
Date: Thu, 16 Jul 2026 16:40:09 +0000 [thread overview]
Message-ID: <178422000988.1338131.13104507118778130998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260710070820.3793624-1-naga.akella@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 10 Jul 2026 12:38:18 +0530 you wrote:
> This series adds the initial plumbing required for Channel Sounding
> reflector support and RAP-side management of CS configuration parameters.
>
> The first patch registers Channel Sounding GATT profiles on reflector
> devices before GATT client discovery checks, ensuring
> org.bluez.ChannelSounding1 interface is available
> when discovery is skipped.
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] rap: Add Channel Sounding parameter types and APIs
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=befde3661e03
- [BlueZ,v1,2/2] src: Register GATT profiles for Channel Sounding reflector
(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:[~2026-07-16 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:08 [PATCH BlueZ v1 0/2] Channel Sounding reflector GATT registration and Naga Bhavani Akella
2026-07-10 7:08 ` [PATCH BlueZ v1 1/2] rap: Add Channel Sounding parameter types and APIs Naga Bhavani Akella
2026-07-10 9:27 ` Channel Sounding reflector GATT registration and bluez.test.bot
2026-07-10 7:08 ` [PATCH BlueZ v1 2/2] src: Register GATT profiles for Channel Sounding reflector Naga Bhavani Akella
2026-07-16 16:40 ` 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=178422000988.1338131.13104507118778130998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=naga.akella@oss.qualcomm.com \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.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