From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/9] Add TMAP & GMAP information services
Date: Mon, 01 Dec 2025 16:50:07 +0000 [thread overview]
Message-ID: <176460780729.2450868.4106997671033738357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1764360140.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 Fri, 28 Nov 2025 22:02:19 +0200 you wrote:
> Add support for TMAP and GMAP services. They contain only device
> audio capability bitmasks.
>
> v2:
> - Rework the service wait to be general mechanism that also determines
> the service autoconnect order.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/9] shared/gmap: add GMAP Service
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f11433431e92
- [BlueZ,v2,2/9] test-gmap: add test for GMAP Service
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5312066e67c8
- [BlueZ,v2,3/9] gmap: Add GMAP profile
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c6b1aed97b6a
- [BlueZ,v2,4/9] doc: org.bluez.MediaEndpoint: add SupportedFeatures
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d4332653009c
- [BlueZ,v2,5/9] bap: add SupportedFeatures for MediaEndpoints
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=71a3aa554f4f
- [BlueZ,v2,6/9] profile: add after_uuids for ordering profile startup
(no matching commit)
- [BlueZ,v2,7/9] device: use after_uuids in service autoconnect and sort also GATT
(no matching commit)
- [BlueZ,v2,8/9] service: add btd_profile::ready callback when after_uuids ready
(no matching commit)
- [BlueZ,v2,9/9] bap: have unicast client wait for VCS & TMAS & GMAP
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-12-01 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 20:02 [PATCH BlueZ v2 0/9] Add TMAP & GMAP information services Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 1/9] shared/gmap: add GMAP Service Pauli Virtanen
2025-11-28 20:58 ` Add TMAP & GMAP information services bluez.test.bot
2025-11-28 20:02 ` [PATCH BlueZ v2 2/9] test-gmap: add test for GMAP Service Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 3/9] gmap: Add GMAP profile Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 4/9] doc: org.bluez.MediaEndpoint: add SupportedFeatures Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 5/9] bap: add SupportedFeatures for MediaEndpoints Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 6/9] profile: add after_uuids for ordering profile startup Pauli Virtanen
2025-12-01 17:00 ` Luiz Augusto von Dentz
2025-12-01 17:32 ` Pauli Virtanen
2025-12-01 17:57 ` Luiz Augusto von Dentz
2025-11-28 20:02 ` [PATCH BlueZ v2 7/9] device: use after_uuids in service autoconnect and sort also GATT Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 8/9] service: add btd_profile::ready callback when after_uuids ready Pauli Virtanen
2025-11-28 20:02 ` [PATCH BlueZ v2 9/9] bap: have unicast client wait for VCS & TMAS & GMAP Pauli Virtanen
2025-12-01 14:43 ` [PATCH BlueZ v2 0/9] Add TMAP & GMAP information services Luiz Augusto von Dentz
2025-12-01 16: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=176460780729.2450868.4106997671033738357.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 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.