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 v2 1/7] doc/btmon: Add GATT database reconstruction guide
Date: Wed, 11 Mar 2026 20:10:09 +0000 [thread overview]
Message-ID: <177325980934.3817440.17208334986003909651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310213314.729718-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 Tue, 10 Mar 2026 17:33:07 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Add a comprehensive section explaining how to reconstruct a remote
> device's GATT database from btsnoop traces. Documents all six phases
> of GATT discovery:
>
> - Primary/Secondary Service Discovery (Read By Group Type)
> - Included Service Discovery (Read By Type with Include UUID)
> - Characteristic Discovery (Read By Type with Characteristic UUID)
> - Descriptor Discovery (Find Information)
> - Characteristic Value Reading (Read Request/Response)
> - Targeted Service Search (Find By Type Value)
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/7] doc/btmon: Add GATT database reconstruction guide
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1d4e2532d4c3
- [BlueZ,v2,2/7] doc/btmon: Add SMP pairing flow documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f247395a18d5
- [BlueZ,v2,3/7] doc/btmon: Add L2CAP channel tracking documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fa9eed625ad3
- [BlueZ,v2,4/7] doc/btmon: Add LE Audio protocol flow documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a0e1d0b5b49c
- [BlueZ,v2,5/7] doc/btmon: Add protocol error codes documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=587f94f9170f
- [BlueZ,v2,6/7] doc/btmon: Add advertising and scanning documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=83f55cc4ad49
- [BlueZ,v2,7/7] doc/btmon: Add BIG Sync flow documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=948d90c274a8
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-03-11 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 21:33 [PATCH BlueZ v2 1/7] doc/btmon: Add GATT database reconstruction guide Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 2/7] doc/btmon: Add SMP pairing flow documentation Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 3/7] doc/btmon: Add L2CAP channel tracking documentation Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 4/7] doc/btmon: Add LE Audio protocol flow documentation Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 5/7] doc/btmon: Add protocol error codes documentation Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 6/7] doc/btmon: Add advertising and scanning documentation Luiz Augusto von Dentz
2026-03-10 21:33 ` [PATCH BlueZ v2 7/7] doc/btmon: Add BIG Sync flow documentation Luiz Augusto von Dentz
2026-03-10 22:39 ` [BlueZ,v2,1/7] doc/btmon: Add GATT database reconstruction guide bluez.test.bot
2026-03-11 20:10 ` 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=177325980934.3817440.17208334986003909651.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox