public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH v2] net: sfp: handle 100G/25G active optical cables in sfp_parse_support
Date: Fri, 18 Aug 2023 12:47:50 +0200	[thread overview]
Message-ID: <6daa226c-4dc8-4c40-8e98-196695839b50@solid-run.com> (raw)
In-Reply-To: <20230817093047.28a2b11d@kernel.org>

Hi Jakub,

Am 17.08.23 um 18:30 schrieb Jakub Kicinski:
> On Mon, 14 Aug 2023 16:17:39 +0200 Josua Mayer wrote:
>> Handle extended compliance code 0x1 (SFF8024_ECC_100G_25GAUI_C2M_AOC)
>> for active optical cables supporting 25G and 100G speeds.
>>
>> Since the specification makes no statement about transmitter range, and
>> as the specific sfp module that had been tested features only 2m fiber -
>> short-range (SR) modes are selected.
> FWIW this got marked as "changes requested" in patchwork by DaveM.
> Since we didn't get an Ack from Russell, would you mind fixing
> the comment style and reposting?
I will post a v3 soon!

      reply	other threads:[~2023-08-18 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 14:17 [PATCH v2] net: sfp: handle 100G/25G active optical cables in sfp_parse_support Josua Mayer
2023-08-15  8:24 ` Simon Horman
2023-08-17 16:30 ` Jakub Kicinski
2023-08-18 10:47   ` Josua Mayer [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=6daa226c-4dc8-4c40-8e98-196695839b50@solid-run.com \
    --to=josua@solid-run.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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