From: patchwork-bot+netdevbpf@kernel.org
To: Moshe Shemesh <moshe@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
pop.adrian61@gmail.com, mkubecek@suse.cz, netdev@vger.kernel.org,
vladyslavt@nvidia.com
Subject: Re: [PATCH net-next 0/8] ethtool: Extend module EEPROM dump API
Date: Mon, 12 Apr 2021 00:10:11 +0000 [thread overview]
Message-ID: <161818621103.2274.14386044370210980683.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1617955601-21055-1-git-send-email-moshe@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 9 Apr 2021 11:06:33 +0300 you wrote:
> Ethtool supports module EEPROM dumps via the `ethtool -m <dev>` command.
> But in current state its functionality is limited - offset and length
> parameters, which are used to specify a linear desired region of EEPROM
> data to dump, is not enough, considering emergence of complex module
> EEPROM layouts such as CMIS 4.0.
> Moreover, CMIS 4.0 extends the amount of pages that may be accessible by
> introducing another parameter for page addressing - banks.
>
> [...]
Here is the summary with links:
- [net-next,1/8] ethtool: Allow network drivers to dump arbitrary EEPROM data
https://git.kernel.org/netdev/net-next/c/c781ff12a2f3
- [net-next,2/8] net/mlx5: Refactor module EEPROM query
https://git.kernel.org/netdev/net-next/c/e19b0a3474ab
- [net-next,3/8] net/mlx5: Implement get_module_eeprom_by_page()
https://git.kernel.org/netdev/net-next/c/e109d2b204da
- [net-next,4/8] net/mlx5: Add support for DSFP module EEPROM dumps
https://git.kernel.org/netdev/net-next/c/4c88fa412a10
- [net-next,5/8] net: ethtool: Export helpers for getting EEPROM info
https://git.kernel.org/netdev/net-next/c/95dfc7effd88
- [net-next,6/8] ethtool: Add fallback to get_module_eeprom from netlink command
https://git.kernel.org/netdev/net-next/c/96d971e307cc
- [net-next,7/8] phy: sfp: add netlink SFP support to generic SFP code
https://git.kernel.org/netdev/net-next/c/d740513f05a2
- [net-next,8/8] ethtool: wire in generic SFP module access
https://git.kernel.org/netdev/net-next/c/c97a31f66ebc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-12 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 8:06 [PATCH net-next 0/8] ethtool: Extend module EEPROM dump API Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 1/8] ethtool: Allow network drivers to dump arbitrary EEPROM data Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 2/8] net/mlx5: Refactor module EEPROM query Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 3/8] net/mlx5: Implement get_module_eeprom_by_page() Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 4/8] net/mlx5: Add support for DSFP module EEPROM dumps Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 5/8] net: ethtool: Export helpers for getting EEPROM info Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 6/8] ethtool: Add fallback to get_module_eeprom from netlink command Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 7/8] phy: sfp: add netlink SFP support to generic SFP code Moshe Shemesh
2021-04-09 8:06 ` [PATCH net-next 8/8] ethtool: wire in generic SFP module access Moshe Shemesh
2021-04-12 0: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=161818621103.2274.14386044370210980683.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pop.adrian61@gmail.com \
--cc=vladyslavt@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.