From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?TWFyacOhbiBQb2zFpcOhayA8bWFyaWFucG9sdGFrQGdtYWlsLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH bluez v2 0/2] shared/gatt-client: Fix init when Service Changed lacks Indicate
Date: Wed, 18 Nov 2026 19:20:08 +0000 [thread overview]
Message-ID: <179502960827.2490531.11541569990427433195.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113-svc-chngd-notify-only-v2-0-e07cc198f32b@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 13 Nov 2026 17:53:39 +0100 you wrote:
> Some devices, e.g. the Aqara Presence Sensor P2 in Matter commissioning
> mode, declare the Service Changed characteristic as Read | Notify only.
> The client initialization then fails because indications are requested
> explicitly, so no services are exported although ServicesResolved is
> set.
>
> Patch 1 requests indications only when the characteristic supports
> them. Patch 2 adds unit tests for both cases.
>
> [...]
Here is the summary with links:
- [bluez,v2,1/2] shared/gatt-client: Fix init when Service Changed lacks Indicate
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0f08061cb4d3
- [bluez,v2,2/2] unit/test-gatt: Add Service Changed registration tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e12013a9bcb1
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:[~2026-11-18 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 16:53 [PATCH bluez v2 0/2] shared/gatt-client: Fix init when Service Changed lacks Indicate Marian Poltak via B4 Relay
2026-11-13 16:53 ` [PATCH bluez v2 1/2] " Marian Poltak via B4 Relay
2026-11-13 16:53 ` [PATCH bluez v2 2/2] unit/test-gatt: Add Service Changed registration tests Marian Poltak via B4 Relay
2026-11-18 19: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=179502960827.2490531.11541569990427433195.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?TWFyacOhbiBQb2zFpcOhayA8bWFyaWFucG9sdGFrQGdtYWlsLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
/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