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 0/9] monitor: Search the frames with a pager
Date: Mon, 21 Sep 2026 14:40:05 +0000 [thread overview]
Message-ID: <179000160589.3063941.11987296756450696856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918161408.2464981-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 Fri, 18 Sep 2026 12:13:59 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> A frame spans several lines, and what identifies one is spread between
> its header and its contents: the header says which controller and when,
> the body says what happened. Searching a trace a line at a time finds the
> line reporting an error without any of that context.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/9] monitor/analyze: Free the channel latency plots
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=482d95704cec
- [BlueZ,v2,2/9] monitor/l2cap: Report the channel latency deviation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=381c58534a2f
- [BlueZ,v2,3/9] monitor/analyze: Drop a trailing space before a newline
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=dd86570d2338
- [BlueZ,v2,4/9] monitor: Route the decoding output through a single function
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=64bf1cefb3c3
- [BlueZ,v2,5/9] monitor: Separate the frames for a pager reading records
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=87051913982c
- [BlueZ,v2,6/9] monitor: Hand the captured frames to the pager on Ctrl-R
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2f7263b64c56
- [BlueZ,v2,7/9] doc/btmon: Document searching the frames
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=97c101c2ef56
- [BlueZ,v2,8/9] monitor: Prefer fzf as the pager when one is not set
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ad10ff49729f
- [BlueZ,v2,9/9] doc/btmon: Document the pager choice
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=17e624d1cd9a
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-21 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 16:13 [PATCH BlueZ v2 0/9] monitor: Search the frames with a pager Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 1/9] monitor/analyze: Free the channel latency plots Luiz Augusto von Dentz
2026-09-18 18:47 ` monitor: Search the frames with a pager bluez.test.bot
2026-09-18 16:14 ` [PATCH BlueZ v2 2/9] monitor/l2cap: Report the channel latency deviation Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 3/9] monitor/analyze: Drop a trailing space before a newline Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 4/9] monitor: Route the decoding output through a single function Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 5/9] monitor: Separate the frames for a pager reading records Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 6/9] monitor: Hand the captured frames to the pager on Ctrl-R Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 7/9] doc/btmon: Document searching the frames Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 8/9] monitor: Prefer fzf as the pager when one is not set Luiz Augusto von Dentz
2026-09-18 16:14 ` [PATCH BlueZ v2 9/9] doc/btmon: Document the pager choice Luiz Augusto von Dentz
2026-09-21 14:40 ` 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=179000160589.3063941.11987296756450696856.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