public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	andrew+netdev@lunn.ch, davem@davemloft.net,
	shenjian15@huawei.com, salil.mehta@huawei.com,
	shaojijie@huawei.com, saeedm@nvidia.com, mbloch@nvidia.com,
	leon@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	gal@nvidia.com, moshe@nvidia.com, shshitrit@nvidia.com,
	ychemla@nvidia.com, jhs@mojatatu.com
Subject: Re: [PATCH net-next V2 0/3] Introduce and use netif_xmit_timeout_ms() helper
Date: Thu, 15 Jan 2026 11:10:11 +0000	[thread overview]
Message-ID: <176847541141.3946378.12441502657710309903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1768209383-1546791-1-git-send-email-tariqt@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 12 Jan 2026 11:16:20 +0200 you wrote:
> Hi,
> 
> This is V2, find V1 here:
> https://lore.kernel.org/all/1764054776-1308696-1-git-send-email-tariqt@nvidia.com/
> 
> This series by Shahar introduces a new helper function
> netif_xmit_timeout_ms() to check if a TX queue has timed out and report
> the timeout duration.
> It also encapsulates the check for whether the TX queue is stopped.
> 
> [...]

Here is the summary with links:
  - [net-next,V2,1/3] net: Introduce netif_xmit_timeout_ms() helper
    https://git.kernel.org/netdev/net-next/c/cfbc8b6babf2
  - [net-next,V2,2/3] net: hns3: Use netif_xmit_timeout_ms() helper
    https://git.kernel.org/netdev/net-next/c/3ae02d659773
  - [net-next,V2,3/3] net/mlx5e: Refine TX timeout handling to skip non-timed-out SQ
    https://git.kernel.org/netdev/net-next/c/b0ba734516d2

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-01-15 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  9:16 [PATCH net-next V2 0/3] Introduce and use netif_xmit_timeout_ms() helper Tariq Toukan
2026-01-12  9:16 ` [PATCH net-next V2 1/3] net: Introduce " Tariq Toukan
2026-01-12  9:16 ` [PATCH net-next V2 2/3] net: hns3: Use " Tariq Toukan
2026-01-12 11:22   ` Jijie Shao
2026-01-12  9:16 ` [PATCH net-next V2 3/3] net/mlx5e: Refine TX timeout handling to skip non-timed-out SQ Tariq Toukan
2026-01-14  9:18 ` [PATCH net-next V2 0/3] Introduce and use netif_xmit_timeout_ms() helper Simon Horman
2026-01-15 11: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=176847541141.3946378.12441502657710309903.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=salil.mehta@huawei.com \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=shshitrit@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=ychemla@nvidia.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