From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 0/9] Add HID over GATT functional tests
Date: Tue, 29 Sep 2026 20:50:13 +0000 [thread overview]
Message-ID: <179071501377.1114983.2390179061802293430.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924154631.369299-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 24 Sep 2026 11:46:22 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds functional tests for HID over GATT (HoG), with bluetoothctl
> registering a HID Service acting as a keyboard, with and without
> Shorter Connection Interval (SCI) support, using the new
> client/scripts/hog-device*.bt scripts, and the HID host:
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/9] shared/gatt-client: Fix calling destroy after unregistering notify
(no matching commit)
- [BlueZ,v3,2/9] attrib: Fix unregistering notifications registered with bt_gatt_client
(no matching commit)
- [BlueZ,v3,3/9] client/gatt: Fix setting descriptor value from scripts
(no matching commit)
- [BlueZ,v3,4/9] client/mgmt: Print Connection Subrate event
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e96e1d7e6db8
- [BlueZ,v3,5/9] emulator: Default to the latest BR/EDR+LE version
(no matching commit)
- [BlueZ,v3,6/9] client/scripts: Add HoG device scripts
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2604ba5035cd
- [BlueZ,v3,7/9] doc: Add functional-hog documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7b68fecf0599
- [BlueZ,v3,8/9] test: functional: add HoG tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c7a2a63a02d6
- [BlueZ,v3,9/9] test: functional: limit the workers by the memory available
(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:[~2026-09-29 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 15:46 [PATCH BlueZ v3 0/9] Add HID over GATT functional tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 1/9] shared/gatt-client: Fix calling destroy after unregistering notify Luiz Augusto von Dentz
2026-09-24 19:16 ` Add HID over GATT functional tests bluez.test.bot
2026-09-24 15:46 ` [PATCH BlueZ v3 2/9] attrib: Fix unregistering notifications registered with bt_gatt_client Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 3/9] client/gatt: Fix setting descriptor value from scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 4/9] client/mgmt: Print Connection Subrate event Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 5/9] emulator: Default to the latest BR/EDR+LE version Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 6/9] client/scripts: Add HoG device scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 7/9] doc: Add functional-hog documentation Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 8/9] test: functional: add HoG tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 9/9] test: functional: limit the workers by the memory available Luiz Augusto von Dentz
2026-09-29 20: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=179071501377.1114983.2390179061802293430.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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 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.