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 v1 00/10] monitor: Reference request frames on responses
Date: Thu, 17 Sep 2026 17:50:05 +0000 [thread overview]
Message-ID: <178966740538.3795449.1357487433014753768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909182840.1289776-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 Wed, 9 Sep 2026 14:28:30 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> A trace shows every request and every response, but nothing ties the two
> together. Finding the request a response belongs to means scrolling back
> through the trace matching identifiers by eye, and the time the other side
> took to answer is only visible by comparing timestamps by hand.
>
> [...]
Here is the summary with links:
- [BlueZ,v1,01/10] monitor: Reference the request frame on command responses
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5a8df006aee2
- [BlueZ,v1,02/10] doc/btmon: Document the request reference on command responses
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f3b1d4d69834
- [BlueZ,v1,03/10] monitor: Resolve commands completed by a later event
(no matching commit)
- [BlueZ,v1,04/10] doc/btmon: Document the deferred command references
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0c926ea1a432
- [BlueZ,v1,05/10] monitor: Report command latency in analyze mode
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0f726ab43454
- [BlueZ,v1,06/10] doc/btmon: Document the command latency statistics
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d70374128764
- [BlueZ,v1,07/10] monitor: Add request tracking for the protocols above HCI
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7b0f38544cd1
- [BlueZ,v1,08/10] monitor/att: Reference the request frame on responses
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a565e23cce68
- [BlueZ,v1,09/10] monitor: Reference the request frame on SDP, AVDTP and AVCTP responses
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c2840bd827af
- [BlueZ,v1,10/10] doc/btmon: Document the protocol request references
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2401054ca67a
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-17 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 18:28 [PATCH BlueZ v1 00/10] monitor: Reference request frames on responses Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 01/10] monitor: Reference the request frame on command responses Luiz Augusto von Dentz
2026-09-10 17:43 ` monitor: Reference request frames on responses bluez.test.bot
2026-09-09 18:28 ` [PATCH BlueZ v1 02/10] doc/btmon: Document the request reference on command responses Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 03/10] monitor: Resolve commands completed by a later event Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 04/10] doc/btmon: Document the deferred command references Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 05/10] monitor: Report command latency in analyze mode Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 06/10] doc/btmon: Document the command latency statistics Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 07/10] monitor: Add request tracking for the protocols above HCI Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 08/10] monitor/att: Reference the request frame on responses Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 09/10] monitor: Reference the request frame on SDP, AVDTP and AVCTP responses Luiz Augusto von Dentz
2026-09-09 18:28 ` [PATCH BlueZ v1 10/10] doc/btmon: Document the protocol request references Luiz Augusto von Dentz
2026-09-17 17: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=178966740538.3795449.1357487433014753768.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