From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
michael.chan@broadcom.com, saeedm@nvidia.com, leon@kernel.org,
ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
f.fainelli@gmail.com, andrew@lunn.ch, mkubecek@suse.cz,
ariela@nvidia.com
Subject: Re: [PATCH net-next v2 0/6] ethtool: add standard FEC statistics
Date: Fri, 16 Apr 2021 00:20:11 +0000 [thread overview]
Message-ID: <161853241123.11262.11625557345112834747.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210415225318.2726095-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 15 Apr 2021 15:53:12 -0700 you wrote:
> This set adds uAPI for reporting standard FEC statistics, and
> implements it in a handful of drivers.
>
> The statistics are taken from the IEEE standard, with one
> extra seemingly popular but not standard statistics added.
>
> The implementation is similar to that of the pause frame
> statistics, user requests the stats by setting a bit
> (ETHTOOL_FLAG_STATS) in the common ethtool header of
> ETHTOOL_MSG_FEC_GET.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] ethtool: move ethtool_stats_init
https://git.kernel.org/netdev/net-next/c/c5797f8a6415
- [net-next,v2,2/6] ethtool: fec_prepare_data() - jump to error handling
https://git.kernel.org/netdev/net-next/c/3d7cc109ecf7
- [net-next,v2,3/6] ethtool: add FEC statistics
https://git.kernel.org/netdev/net-next/c/be85dbfeb37c
- [net-next,v2,4/6] bnxt: implement ethtool::get_fec_stats
https://git.kernel.org/netdev/net-next/c/c9ca5c3aabaf
- [net-next,v2,5/6] sfc: ef10: implement ethtool::get_fec_stats
https://git.kernel.org/netdev/net-next/c/cab351be53c2
- [net-next,v2,6/6] mlx5: implement ethtool::get_fec_stats
https://git.kernel.org/netdev/net-next/c/1703bb50df0e
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:[~2021-04-16 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 22:53 [PATCH net-next v2 0/6] ethtool: add standard FEC statistics Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 1/6] ethtool: move ethtool_stats_init Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 2/6] ethtool: fec_prepare_data() - jump to error handling Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 3/6] ethtool: add FEC statistics Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 4/6] bnxt: implement ethtool::get_fec_stats Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 5/6] sfc: ef10: " Jakub Kicinski
2021-04-20 15:13 ` Edward Cree
2021-04-20 18:24 ` Jakub Kicinski
2021-04-15 22:53 ` [PATCH net-next v2 6/6] mlx5: " Jakub Kicinski
2021-04-15 23:51 ` [PATCH net-next v2 0/6] ethtool: add standard FEC statistics Saeed Mahameed
2021-04-16 0:20 ` patchwork-bot+netdevbpf [this message]
2021-05-18 6:48 ` huangguangbin (A)
2021-05-18 17:30 ` Jakub Kicinski
2021-07-01 12:18 ` huangguangbin (A)
2021-07-01 15:42 ` Jakub Kicinski
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=161853241123.11262.11625557345112834747.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ariela@nvidia.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).