From: patchwork-bot+netdevbpf@kernel.org
To: Peter Hunt <peter.hunt@opengear.com>
Cc: netdev@vger.kernel.org, loic.poulain@oss.qualcomm.com,
ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
dnlplm@gmail.com
Subject: Re: [PATCH net-next v2] net: wwan: mhi_wwan_ctrl: say the DTR drop flush is best effort
Date: Thu, 19 Nov 2026 00:10:13 +0000 [thread overview]
Message-ID: <179504701302.2637749.17906773480423689958.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112172216.31216-1-peter.hunt@opengear.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Nov 2026 10:22:16 -0700 you wrote:
> Four comments around the DTR/RTS work don't match the code since
> commit 10f51f4fb99d ("net: wwan: mhi_wwan_ctrl: send a DTR drop before
> it can be coalesced"):
>
> - the ->dtr_rts() comment says the drop is sent now, but a drop that
> hits a full UL ring or a failed allocation is retried with whatever
> state is latest by then,
> - the stop() comment says pending state is sent before the channel
> stops, but the flush there makes one attempt as well, and a retry
> goes out from dtr_work after the channel has stopped,
> - the dtr_mdmbits comment only describes coalescing,
> - the remove() comment says the removal drop gets one attempt, but the
> drop and stop() paths now flush the work as well.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: wwan: mhi_wwan_ctrl: say the DTR drop flush is best effort
https://git.kernel.org/netdev/net-next/c/84a828d40fae
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-11-19 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 17:22 [PATCH net-next v2] net: wwan: mhi_wwan_ctrl: say the DTR drop flush is best effort Peter Hunt
2026-11-13 8:20 ` Loic Poulain
2026-11-19 0:10 ` patchwork-bot+netdevbpf [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=179504701302.2637749.17906773480423689958.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dnlplm@gmail.com \
--cc=edumazet@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter.hunt@opengear.com \
--cc=ryazanov.s.a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.