public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v4 1/2] org.bluez.Media: add SupportedFeatures
Date: Tue, 06 May 2025 15:00:28 +0000	[thread overview]
Message-ID: <174654362899.1554625.910351840236203317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6df15922fc4f602c9b10baf640e07859c4d3e958.1746256909.git.pav@iki.fi>

Hello:

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

On Sat,  3 May 2025 10:24:25 +0300 you wrote:
> Add SupportedFeatures property for feature information that applications
> cannot find otherwise.
> 
> Add feature tx-timestamping. Applications cannot enable it on old BlueZ
> versions without that feature, as it requires special handling on BlueZ
> side.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v4,1/2] org.bluez.Media: add SupportedFeatures
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=30d2de12868d
  - [BlueZ,v4,2/2] media: implement SupportedFeatures property
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9ea27141c71f

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



      parent reply	other threads:[~2025-05-06 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-03  7:24 [PATCH BlueZ v4 1/2] org.bluez.Media: add SupportedFeatures Pauli Virtanen
2025-05-03  7:24 ` [PATCH BlueZ v4 2/2] media: implement SupportedFeatures property Pauli Virtanen
2025-05-03  8:50 ` [BlueZ,v4,1/2] org.bluez.Media: add SupportedFeatures bluez.test.bot
2025-05-06 15:00 ` 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=174654362899.1554625.910351840236203317.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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