Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1] shared/rap: Track RAS CCC state per connection
Date: Mon, 12 Oct 2026 21:50:11 +0000	[thread overview]
Message-ID: <179184181126.4115061.339294852166421514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009173341.1143848-1-luiz.dentz@gmail.com>

Hello:

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

On Fri,  9 Oct 2026 13:33:41 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> The Real-time, On-demand, Ranging Data Ready and Ranging Data Overwritten
> CCC values were stored on the RAS service shared by all connections, while
> ranging data is sent on the ATT channel of the connection that produced
> it. One central's subscription could therefore decide whether, and with
> which transport, another central was sent ranging data, and the Real-time
> vs On-demand exclusivity check rejected a central because of another
> central's configuration.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1] shared/rap: Track RAS CCC state per connection
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=da2406695f70

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-10-12 21:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 17:33 [PATCH BlueZ v1] shared/rap: Track RAS CCC state per connection Luiz Augusto von Dentz
2026-10-09 19:52 ` [BlueZ,v1] " bluez.test.bot
2026-10-10  0:36 ` bluez.test.bot
2026-10-12 21:50 ` 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=179184181126.4115061.339294852166421514.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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