From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Moshe Shemesh <moshe@mellanox.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Adrian Pop <pop.adrian61@gmail.com>,
"Michal Kubecek" <mkubecek@suse.cz>, <netdev@vger.kernel.org>,
Vladyslav Tarasiuk <vladyslavt@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>
Subject: Re: [PATCH net-next v2 1/2] ethtool: Add CMIS 4.0 module type to UAPI
Date: Mon, 23 Nov 2020 14:40:11 -0800 [thread overview]
Message-ID: <20201123144011.0000713e@intel.com> (raw)
In-Reply-To: <1606123198-6230-2-git-send-email-moshe@mellanox.com>
Moshe Shemesh wrote:
> From: Vladyslav Tarasiuk <vladyslavt@nvidia.com>
>
> CMIS 4.0 document describes a universal EEPROM memory layout, which is
> used for some modules such as DSFP, OSFP and QSFP-DD modules. In order
> to distinguish them in userspace from existing standards, add
> corresponding values.
>
> CMIS 4.0 EERPOM memory includes mandatory and optional pages, the max
typo? s/EERPOM/EEPROM
> read length 768B includes passive and active cables mandatory pages.
>
> Signed-off-by: Vladyslav Tarasiuk <vladyslavt@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
rest was ok.
next prev parent reply other threads:[~2020-11-23 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 9:19 [PATCH net-next v2 0/2] Add support for DSFP transceiver type Moshe Shemesh
2020-11-23 9:19 ` [PATCH net-next v2 1/2] ethtool: Add CMIS 4.0 module type to UAPI Moshe Shemesh
2020-11-23 22:40 ` Jesse Brandeburg [this message]
2020-11-25 10:41 ` Moshe Shemesh
2020-11-23 9:19 ` [PATCH net-next v2 2/2] net/mlx5e: Add DSFP EEPROM dump support to ethtool Moshe Shemesh
2020-11-24 1:14 ` [PATCH net-next v2 0/2] Add support for DSFP transceiver type Andrew Lunn
2020-11-24 21:16 ` Jakub Kicinski
2020-11-25 10:40 ` Moshe Shemesh
2020-11-25 14:18 ` Andrew Lunn
2020-11-26 14:23 ` Moshe Shemesh
2020-11-26 15:21 ` Andrew Lunn
2020-11-27 15:12 ` Moshe Shemesh
2020-11-27 15:56 ` Andrew Lunn
2020-12-29 10:23 ` Vladyslav Tarasiuk
2020-12-29 16:25 ` Andrew Lunn
2020-12-30 13:55 ` Vladyslav Tarasiuk
2020-12-30 15:36 ` Andrew Lunn
2021-01-04 15:24 ` Vladyslav Tarasiuk
2021-01-04 15:48 ` Andrew Lunn
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=20201123144011.0000713e@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=moshe@mellanox.com \
--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 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).