All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	mohsin.bashr@gmail.com, vadim.fedorenko@linux.dev,
	jacob.e.keller@intel.com
Subject: Re: [PATCH net-next v2 0/6] eth: fbnic: Extend hw stats support
Date: Thu, 28 Aug 2025 02:00:35 +0000	[thread overview]
Message-ID: <175634643523.908900.2000854189315078878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250825200206.2357713-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 25 Aug 2025 13:02:00 -0700 you wrote:
> Mohsin says:
> 
> Extend hardware stats support for fbnic by adding the ability to reset
> hardware stats when the device experience a reset due to a PCI error and
> include MAC stats in the hardware stats reset. Additionally, expand
> hardware stats coverage to include FEC, PHY, and Pause stats.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] eth: fbnic: Move hw_stats_lock out of fbnic_dev
    https://git.kernel.org/netdev/net-next/c/2ee5c8c0c28e
  - [net-next,v2,2/6] eth: fbnic: Reset hw stats upon PCI error
    https://git.kernel.org/netdev/net-next/c/b1161b1863c5
  - [net-next,v2,3/6] eth: fbnic: Reset MAC stats
    https://git.kernel.org/netdev/net-next/c/bcf54e5d7cd0
  - [net-next,v2,4/6] eth: fbnic: Fetch PHY stats from device
    https://git.kernel.org/netdev/net-next/c/df4c5d9a290e
  - [net-next,v2,5/6] eth: fbnic: Read PHY stats via the ethtool API
    https://git.kernel.org/netdev/net-next/c/33c493791bc0
  - [net-next,v2,6/6] eth: fbnic: Add pause stats support
    https://git.kernel.org/netdev/net-next/c/e9faf4db5f26

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-08-28  2:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 20:02 [PATCH net-next v2 0/6] eth: fbnic: Extend hw stats support Jakub Kicinski
2025-08-25 20:02 ` [PATCH net-next v2 1/6] eth: fbnic: Move hw_stats_lock out of fbnic_dev Jakub Kicinski
2025-08-26 23:31   ` Jacob Keller
2025-08-25 20:02 ` [PATCH net-next v2 2/6] eth: fbnic: Reset hw stats upon PCI error Jakub Kicinski
2025-08-26 23:32   ` Jacob Keller
2025-08-25 20:02 ` [PATCH net-next v2 3/6] eth: fbnic: Reset MAC stats Jakub Kicinski
2025-08-26 23:33   ` Jacob Keller
2025-08-25 20:02 ` [PATCH net-next v2 4/6] eth: fbnic: Fetch PHY stats from device Jakub Kicinski
2025-08-26 23:35   ` Jacob Keller
2025-08-25 20:02 ` [PATCH net-next v2 5/6] eth: fbnic: Read PHY stats via the ethtool API Jakub Kicinski
2025-08-26 23:35   ` Jacob Keller
2025-08-25 20:02 ` [PATCH net-next v2 6/6] eth: fbnic: Add pause stats support Jakub Kicinski
2025-08-26 23:36   ` Jacob Keller
2025-08-28  2:00 ` 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=175634643523.908900.2000854189315078878.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=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=mohsin.bashr@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    /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.