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] monitor: Print unacked frame when releasing them
Date: Thu, 14 Aug 2025 17:20:09 +0000 [thread overview]
Message-ID: <175519200950.380512.10064199577915217402.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250814154156.8221-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 14 Aug 2025 11:41:56 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This attempts to print the frame number of frames considered unacked
> (missing NOCP):
>
> > HCI Event: Disconnect Complete (0x05) plen 4
> Status: Success (0x00)
> Handle: 2304 Address: XX:XX:XX:XX:XX:XX
> Reason: Connection Terminated By Local Host (0x16)
> [0]#102132 unacked
> [1]#102137 unacked
> [2]#102139 unacked
> [3]#102141 unacked
> [4]#102143 unacked
> [5]#102145 unacked
> [6]#102147 unacked
> [7]#102150 unacked
>
> [...]
Here is the summary with links:
- [BlueZ,v1] monitor: Print unacked frame when releasing them
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ce82168f9f70
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:[~2025-08-14 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 15:41 [PATCH BlueZ v1] monitor: Print unacked frame when releasing them Luiz Augusto von Dentz
2025-08-14 17:10 ` [BlueZ,v1] " bluez.test.bot
2025-08-14 17:20 ` 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=175519200950.380512.10064199577915217402.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