From: patchwork-bot+bluetooth@kernel.org
To: Qiqi Zhang <eddy.zhang@rock-chips.com>
Cc: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org
Subject: Re: [PATCH v2] Bluetooth: hci_h5: Complements reliable packet processing logic
Date: Thu, 06 Apr 2023 21:00:20 +0000 [thread overview]
Message-ID: <168081482085.2619.8551087940289417594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230404022711.86515-1-eddy.zhang@rock-chips.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 4 Apr 2023 10:27:11 +0800 you wrote:
> As shown in the schematic diagram below.There may be a critical
> scenario in the current code. If the device does not receive an
> pure ack sent by the host due to insufficient receive buffer or
> other reasons and triggers a retransmission, the host will always
> be in an 'out-of-order' state.The state machine will get stuck.
>
> host device
> SEQ3,ACK4 --------->
> <--------- SEQ4,ACK4
> pure ACK ---------> (not received)
> (out-of-order) <--------- SEQ4,ACK4(retransmission)
> ........
> (out-of-order) <--------- SEQ4,ACK4(retransmission)
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_h5: Complements reliable packet processing logic
https://git.kernel.org/bluetooth/bluetooth-next/c/13a6ebae665d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-06 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:29 [PATCH] Bluetooth: hci_h5: Complements reliable packet processing logic Qiqi Zhang
2023-04-04 2:27 ` [PATCH v2] " Qiqi Zhang
2023-04-06 21:00 ` patchwork-bot+bluetooth [this message]
2023-04-06 21:00 ` [PATCH] " patchwork-bot+bluetooth
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=168081482085.2619.8551087940289417594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=eddy.zhang@rock-chips.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/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