From: patchwork-bot+netdevbpf@kernel.org
To: Mingj Ye <insyelu@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, nic_swsd@realtek.com,
tiwai@suse.de, hayeswang@realtek.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: usb: r8152: fix transmit queue timeout
Date: Wed, 21 Jan 2026 02:40:36 +0000 [thread overview]
Message-ID: <176896323659.699622.12478505738537738657.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120015949.84996-1-insyelu@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Jan 2026 09:59:49 +0800 you wrote:
> When the TX queue length reaches the threshold, the netdev watchdog
> immediately detects a TX queue timeout.
>
> This patch updates the trans_start timestamp of the transmit queue
> on every asynchronous USB URB submission along the transmit path,
> ensuring that the network watchdog accurately reflects ongoing
> transmission activity.
>
> [...]
Here is the summary with links:
- [v2] net: usb: r8152: fix transmit queue timeout
https://git.kernel.org/netdev/net-next/c/833dcd75d54f
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:[~2026-01-21 2:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 1:59 [PATCH v2] net: usb: r8152: fix transmit queue timeout Mingj Ye
2026-01-20 2:49 ` Hayes Wang
2026-01-21 2:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-19 10:56 insyelu
2026-01-19 11:07 ` Greg KH
2026-01-19 2:28 insyelu
2026-01-19 6:40 ` Greg KH
2026-01-14 2:56 [PATCH] " insyelu
2026-01-16 2:37 ` [PATCH v2] " insyelu
2026-01-16 17:32 ` Andrew Lunn
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=176896323659.699622.12478505738537738657.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.com \
--cc=insyelu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=tiwai@suse.de \
/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