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 00/10] Add TMAP & GMAP information services
Date: Wed, 26 Nov 2025 16:20:07 +0000	[thread overview]
Message-ID: <176417400728.1749268.5224595081449204444.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1763914558.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 Sun, 23 Nov 2025 18:17:05 +0200 you wrote:
> Add support for TMAP and GMAP services. They contain only device
> audio capability bitmasks.
> 
> Expose the values from remote devices in
> org.bluez.MediaEndpoint->SupportedFeatures
> 
> Not sure if this should be org.bluez.Device->SupportedFeatures instead.
> 
> [...]

Here is the summary with links:
  - [BlueZ,01/10] shared/tmap: add TMAP Service
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=12e32efac2e4
  - [BlueZ,02/10] test-tmap: add test for TMAP Service
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7b93dae26a57
  - [BlueZ,03/10] tmap: add TMAP profile
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0f56b20f9196
  - [BlueZ,04/10] bap: have unicast client wait for VCS & TMAS
    (no matching commit)
  - [BlueZ,05/10] shared/gmap: add GMAP Service
    (no matching commit)
  - [BlueZ,06/10] test-gmap: add test for GMAP Service
    (no matching commit)
  - [BlueZ,07/10] gmap: Add GMAP profile
    (no matching commit)
  - [BlueZ,08/10] bap: unicast client wait for GMAP service
    (no matching commit)
  - [BlueZ,09/10] doc: org.bluez.MediaEndpoint: add SupportedFeatures
    (no matching commit)
  - [BlueZ,10/10] bap: add SupportedFeatures for MediaEndpoints
    (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:[~2025-11-26 16:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 16:17 [PATCH BlueZ 00/10] Add TMAP & GMAP information services Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 01/10] shared/tmap: add TMAP Service Pauli Virtanen
2025-11-23 17:24   ` Add TMAP & GMAP information services bluez.test.bot
2025-11-23 16:17 ` [PATCH BlueZ 02/10] test-tmap: add test for TMAP Service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 03/10] tmap: add TMAP profile Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 04/10] bap: have unicast client wait for VCS & TMAS Pauli Virtanen
2025-11-24 16:25   ` Luiz Augusto von Dentz
2025-11-24 16:58     ` Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 05/10] shared/gmap: add GMAP Service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 06/10] test-gmap: add test for " Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 07/10] gmap: Add GMAP profile Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 08/10] bap: unicast client wait for GMAP service Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 09/10] doc: org.bluez.MediaEndpoint: add SupportedFeatures Pauli Virtanen
2025-11-24 16:20   ` Luiz Augusto von Dentz
2025-11-24 16:55     ` Pauli Virtanen
2025-11-23 16:17 ` [PATCH BlueZ 10/10] bap: add SupportedFeatures for MediaEndpoints Pauli Virtanen
2025-11-26 16:20 ` 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=176417400728.1749268.5224595081449204444.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