All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch, gal@nvidia.com,
	leonro@nvidia.com, ychemla@nvidia.com, saeedm@nvidia.com,
	leon@kernel.org, corbet@lwn.net, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	kalesh-anakkur.purayil@broadcom.com, jacob.e.keller@intel.com,
	stfomichev@gmail.com
Subject: Re: [PATCH net-next V2 0/4] mlx5e: Support recovery counter in reset
Date: Fri, 21 Mar 2025 20:30:33 +0000	[thread overview]
Message-ID: <174258903353.2613064.2638906472683771245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1742112876-2890-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 Sun, 16 Mar 2025 10:14:32 +0200 you wrote:
> Hi,
> 
> This series by Yael adds a recovery counter in ethtool, for any recovery
> type during port reset cycle.
> Series starts with some cleanup and refactoring patches.
> New counter is added and exposed to ethtool stats in patch #4.
> 
> [...]

Here is the summary with links:
  - [net-next,V2,1/4] net/mlx5e: Ensure each counter group uses its PCAM bit
    https://git.kernel.org/netdev/net-next/c/8e6f6e92d3fe
  - [net-next,V2,2/4] net/mlx5e: Access PHY layer counter group as other counter groups
    https://git.kernel.org/netdev/net-next/c/da4fa5d8817d
  - [net-next,V2,3/4] net/mlx5e: Get counter group size by FW capability
    https://git.kernel.org/netdev/net-next/c/4c737ceb690c
  - [net-next,V2,4/4] net/mlx5e: Expose port reset cycle recovery counter via ethtool
    https://git.kernel.org/netdev/net-next/c/c3b999cad7ec

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-03-21 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16  8:14 [PATCH net-next V2 0/4] mlx5e: Support recovery counter in reset Tariq Toukan
2025-03-16  8:14 ` [PATCH net-next V2 1/4] net/mlx5e: Ensure each counter group uses its PCAM bit Tariq Toukan
2025-03-16  8:14 ` [PATCH net-next V2 2/4] net/mlx5e: Access PHY layer counter group as other counter groups Tariq Toukan
2025-03-16  8:14 ` [PATCH net-next V2 3/4] net/mlx5e: Get counter group size by FW capability Tariq Toukan
2025-03-16  8:14 ` [PATCH net-next V2 4/4] net/mlx5e: Expose port reset cycle recovery counter via ethtool Tariq Toukan
2025-03-21 20:30 ` 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=174258903353.2613064.2638906472683771245.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=stfomichev@gmail.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 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.