public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 1/3] monitor: Add L2CAP channel details to analyze output
Date: Thu, 16 Apr 2026 13:50:04 +0000	[thread overview]
Message-ID: <177634740480.2827737.2643221147708039593.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260415205818.594024-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, 15 Apr 2026 16:58:16 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> Enhance btmon analyze mode to display richer per-channel information:
> 
> - Add MTU, MPS, and mode fields to struct l2cap_chan
> - Parse Configure Request/Response options for BR/EDR channels to
>   extract MTU (option 0x01) and mode (option 0x04)
> - Add l2cap_le_sig() to parse LE signaling (CID 5) for LE Credit
>   Based Connection Request/Response and Enhanced Credit Connection
>   Request, extracting PSM, MTU, MPS, and mode
> - Display fixed channel names (ATT, L2CAP Signaling, SMP) for CID <= 7
> - Show PSM in both decimal and hex format
> - Print mode, MTU, and MPS for dynamic channels
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/3] monitor: Add L2CAP channel details to analyze output
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6b4c21721c80
  - [BlueZ,v1,2/3] monitor: Use wall-clock duration for throughput and add min/max speed
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ebeceecd3ccb
  - [BlueZ,v1,3/3] doc: Add throughput estimation section to btmon-l2cap.rst
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f360d9e4428d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-16 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 20:58 [PATCH BlueZ v1 1/3] monitor: Add L2CAP channel details to analyze output Luiz Augusto von Dentz
2026-04-15 20:58 ` [PATCH BlueZ v1 2/3] monitor: Use wall-clock duration for throughput and add min/max speed Luiz Augusto von Dentz
2026-04-15 20:58 ` [PATCH BlueZ v1 3/3] doc: Add throughput estimation section to btmon-l2cap.rst Luiz Augusto von Dentz
2026-04-15 22:10 ` [BlueZ,v1,1/3] monitor: Add L2CAP channel details to analyze output bluez.test.bot
2026-04-16 13: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=177634740480.2827737.2643221147708039593.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