All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: Meir Lichtinger <meirl@mellanox.com>,
	Aya Levin <ayal@mellanox.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"rmk+kernel@armlinux.org.uk" <rmk+kernel@armlinux.org.uk>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] ethtool: Add support for 100Gbps per lane link modes
Date: Thu, 25 Jun 2020 23:31:48 +0200	[thread overview]
Message-ID: <20200625213148.GB535869@lunn.ch> (raw)
In-Reply-To: <df18c2c0a9b160bfabe0e4ba7f251e789a9d7d7c.camel@mellanox.com>

> Hi Andrew,
> 
> we are going to update the commit message with:
> 
>     LR, ER and FR are defined as a single link mode because they are
>     using same technology and by design are fully interoperable.
>     EEPROM content indicates if the module is LR, ER, or FR, and the
>     user space ethtool decoder is planned to support decoding these    
>     modes in the EEPROM.
> 
> Please let me know it this answer your questions, so we can re-spin
> this patch.

Hi Saeed.

This looks good to me.

Thanks
	Andrew

  reply	other threads:[~2020-06-25 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 23:41 [PATCH net-next 0/2] ethtool: Add support for 100Gbps per lane link modes Saeed Mahameed
2020-04-30 23:41 ` [PATCH net-next 1/2] " Saeed Mahameed
2020-05-02 15:08   ` Andrew Lunn
2020-06-11 13:19     ` Meir Lichtinger
2020-06-11 13:54       ` Andrew Lunn
2020-06-11 18:52         ` Meir Lichtinger
2020-06-25 20:24       ` Saeed Mahameed
2020-06-25 21:31         ` Andrew Lunn [this message]
2020-04-30 23:41 ` [PATCH net-next 2/2] net/mlx5: Added " Saeed Mahameed
2020-05-01 22:59 ` [PATCH net-next 0/2] ethtool: Add " David Miller

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=20200625213148.GB535869@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ayal@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=meirl@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=saeedm@mellanox.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.