Linux bluetooth development
 help / color / mirror / Atom feed
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] unit/test-rap: Add PTS tests for CS
Date: Tue, 04 Aug 2026 17:30:06 +0000	[thread overview]
Message-ID: <178586460663.3699428.2074535802813189487.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260731131352.3154342-1-naga.akella@oss.qualcomm.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 31 Jul 2026 18:43:52 +0530 you wrote:
> RAS/SR/SGGIT/CHA/BV-05-C - Verifies the Ranging Data Ready characteristic
> exists in the GATT database with exactly the Indicate property
> RAS/SR/SGGIT/CHA/BV-06-C - Same characteristic-existence/property check,
> for an IUT configured to support both Indicate and Notify
> RAS/SR/SGGIT/CHA/BV-07-C - Same check, for an IUT supporting Indicate
> and Read on Ranging Data Ready
> RAS/SR/SGGIT/CHA/BV-08-C - Same check, for an IUT supporting all three
> Indicate, Notify, and Read
> RAS/SR/SGGIT/CHA/BV-09-C - Verifies the Ranging Data Overwritten char
> exists with exactly the Indicate
> RAS/SR/SGGIT/CHA/BV-10-C - Same check, for Indicate and Notify support
> RAS/SR/SGGIT/CHA/BV-11-C - Same check, for Indicate and Read support
> RAS/SR/SGGIT/CHA/BV-12-C - Same check, for Indicate, Notify and Read
> support
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1] unit/test-rap: Add PTS tests for CS
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=690c16df6067

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-04 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 13:13 [PATCH BlueZ v1] unit/test-rap: Add PTS tests for CS Naga Bhavani Akella
2026-07-31 14:50 ` [BlueZ,v1] " bluez.test.bot
2026-08-04 17:30 ` 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=178586460663.3699428.2074535802813189487.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