From: patchwork-bot+bluetooth@kernel.org
To: dt <derektern@proton.me>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v5 1/3] shared/bap: Skip local metadata Config callbacks
Date: Fri, 18 Sep 2026 17:20:07 +0000 [thread overview]
Message-ID: <178975200713.1061421.865108747218478058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ys4-B1PGqhV2wgPjUFnZLGOi_QkoCs1ZyOZl679pGV8nNJLfR28E4wDuGQti0eyGwIYHgFGa4GqfTi5Vg_nvOqQBqEhRaTlA_D9MxgEblZo=@proton.me>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 17 Sep 2026 19:12:04 +0000 you wrote:
> From: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
>
> When reconfiguring a client stream that is already Codec Configured,
> setup_config() queues Codec Configuration and then caches metadata.
> stream_metadata() emits a same-state CONFIG notification for that local
> update. The profile callback treats it as the peer's configuration
> completion and clears config_pending before the peer has responded.
>
> [...]
Here is the summary with links:
- [BlueZ,v5,1/3] shared/bap: Skip local metadata Config callbacks
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=11bf67364e55
- [BlueZ,v5,2/3] client: Pass unicast preset metadata to config
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=72a5ce497f34
- [BlueZ,v5,3/3] test-functional: Cover BAP metadata reconfiguration
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-18 17:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 10:28 [PATCH BlueZ 0/2] Avoid local metadata Config notifications dt
2026-09-16 10:29 ` [PATCH BlueZ 1/2] shared/bap: Skip local metadata Config callbacks dt
2026-09-16 15:28 ` Avoid local metadata Config notifications bluez.test.bot
2026-09-16 17:11 ` [PATCH BlueZ 1/2] shared/bap: Skip local metadata Config callbacks Luiz Augusto von Dentz
2026-09-16 17:29 ` Luiz Augusto von Dentz
2026-09-17 14:35 ` dt
2026-09-17 14:37 ` [PATCH BlueZ v2 " dt
2026-09-17 14:39 ` [PATCH BlueZ v2 2/2] unit: Test metadata during BAP client reconfig dt
2026-10-01 15:44 ` Avoid local metadata Config notifications bluez.test.bot
2026-09-16 10:31 ` [PATCH BlueZ 2/2] unit: Test metadata during BAP client reconfig dt
2026-09-17 14:47 ` Luiz Augusto von Dentz
2026-09-17 15:28 ` [PATCH BlueZ v3 1/2] shared/bap: Skip local metadata Config callbacks dt
2026-09-17 15:30 ` [PATCH BlueZ v3 2/2] test-functional: Cover BAP metadata reconfiguration dt
2026-09-17 16:21 ` Luiz Augusto von Dentz
2026-09-17 17:00 ` [PATCH BlueZ v4 1/2] shared/bap: Skip local metadata Config callbacks dt
2026-09-17 17:03 ` [PATCH BlueZ v4 2/2] test-functional: Cover BAP metadata reconfiguration dt
2026-09-17 17:32 ` Luiz Augusto von Dentz
2026-09-17 19:12 ` [PATCH BlueZ v5 1/3] shared/bap: Skip local metadata Config callbacks dt
2026-09-17 19:15 ` [PATCH BlueZ v5 2/3] client: Pass unicast preset metadata to config dt
2026-09-17 19:19 ` [PATCH BlueZ v5 3/3] test-functional: Cover BAP metadata reconfiguration dt
2026-09-17 21:11 ` [BlueZ,v5,1/3] shared/bap: Skip local metadata Config callbacks bluez.test.bot
2026-09-18 17:20 ` patchwork-bot+bluetooth [this message]
2026-10-02 21:01 ` bluez.test.bot
2026-09-17 18:06 ` [BlueZ,v3,1/2] " bluez.test.bot
[not found] <IGuo=5FED6hoZcdNfKi5TCkYNNfYCJKn1CUSYS4a4ZNZ9WjaZCMI3rmBzLoslV22TvEjShB4iyBBAec3nrM4mMGI=5Fr8dHKBUfAGLjZxXmgfIE=3D@proton.me>
[not found] ` <pEIogdpm1KrQokz6n7Vp2rMm4FqyjlQ2X2YtxXFBhhWy=5FIaqXXNp8K7EwDeohmT6yelHFNOy7IuYYi7ooLtT2zeODVf8LPoBiOTrs7ua3O4=3D@proton.me>
[not found] ` <CABBYNZ+hzc=5Fv=5Ft5xtwsMPDzrhFgLzUwcN6QmABy=5F=3DGqJjMHEHg@mail.gmail.com>
[not found] ` <6TMaqpYkRT0WXnrX1OlkxzNfaStK17vM4wQJWLFJWEP4ZZ=5FVRyfVhUEMg8KwzWWQzOsyUY8zEzSg1SBT04BDh9F9yC4Y9rft9GtBAzekwF4=3D@proton.me>
[not found] ` <70Tk7oozT7RMA83SmYEKlhm5sNES1V664l63179SDXwOnzZnXOurvxWa-gGmSDBQ=5FOS7=5F2m1ibyKcUr1=5FCBNoNFsnm-PdGGSOWGeXsgBH9k=3D@proton.me>
[not found] ` <CABBYNZ+OqjfHErzn96k6vw=5Fend=5FLLM8uECOgyeuncTxt0MJFFA@mail.gmail.com>
[not found] ` <BL2ma9jjRAUeT3MnEg6XM7bojQ-aauPDy75cebC98yo5E9OVFN0uhsKtemymwe6669o08bpgH5T9=5Ftqgx9tZ9NISnATcThQ8fJ4qujO7fZE=3D@proton.me>
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=178975200713.1061421.865108747218478058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=derektern@proton.me \
--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