All of lore.kernel.org
 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, nakella@qti.qualcomm.com
Subject: Re: [PATCH BlueZ v3 0/7]  Add ranging provider implementation
Date: Wed, 02 Sep 2026 17:10:06 +0000	[thread overview]
Message-ID: <178836900639.2851456.8688573882939387333.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827052034.1374180-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 Thu, 27 Aug 2026 10:50:27 +0530 you wrote:
> From: Naga Bhavani Akella <nakella@qti.qualcomm.com>
> 
> This series documents and implements the D-Bus API that lets an
> external ranging daemon compute Channel Sounding distance estimates
> from the raw procedure data BlueZ reports, and feed them back for
> reflection on the device's Channel Sounding interface
> 
> [...]

Here is the summary with links:
  - [BlueZ,v3,1/7] doc: Add org.bluez.Ranging1 documentation
    (no matching commit)
  - [BlueZ,v3,2/7] doc: Add org.bluez.RangingProvider1 documentation
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0654aa95ce08
  - [BlueZ,v3,3/7] doc: Add org.bluez.RangingProviderManager1 documentation
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=da77259717e4
  - [BlueZ,v3,4/7] doc: Modify bluetoothctl-cs documentation
    (no matching commit)
  - [BlueZ,v3,5/7] src: Add Ranging provider D-Bus API
    (no matching commit)
  - [BlueZ,v3,6/7] client: Add ranging distance display support to bluetoothctl
    (no matching commit)
  - [BlueZ,v3,7/7] test: Add Python Ranging Provider example
    (no matching commit)

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-09-02 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  5:20 [PATCH BlueZ v3 0/7] Add ranging provider implementation Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 1/7] doc: Add org.bluez.Ranging1 documentation Naga Bhavani Akella
2026-08-27 16:16   ` Add ranging provider implementation bluez.test.bot
2026-09-11 18:26   ` bluez.test.bot
2026-08-27  5:20 ` [PATCH BlueZ v3 2/7] doc: Add org.bluez.RangingProvider1 documentation Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 3/7] doc: Add org.bluez.RangingProviderManager1 documentation Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 4/7] doc: Modify bluetoothctl-cs documentation Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 5/7] src: Add Ranging provider D-Bus API Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 6/7] client: Add ranging distance display support to bluetoothctl Naga Bhavani Akella
2026-08-27  5:20 ` [PATCH BlueZ v3 7/7] test: Add Python Ranging Provider example Naga Bhavani Akella
2026-09-02 17:10 ` 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=178836900639.2851456.8688573882939387333.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=nakella@qti.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 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.