From: David Miller <davem@davemloft.net>
To: linux@armlinux.org.uk
Cc: andrew@lunn.ch, hkallweit1@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, pali@kernel.org
Subject: Re: [PATCH RESEND net-next 0/2] Add support for VSOL V2801F/CarlitoxxPro CPGOS03 GPON module
Date: Wed, 09 Dec 2020 19:38:47 -0800 (PST) [thread overview]
Message-ID: <20201209.193847.1853316342833410585.davem@davemloft.net> (raw)
In-Reply-To: <20201209112152.GT1551@shell.armlinux.org.uk>
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Date: Wed, 9 Dec 2020 11:21:52 +0000
> Hi,
>
> This patch set adds support for the V2801F / CarlitoxxPro module. This
> requires two changes:
>
> 1) the module only supports single byte reads to the ID EEPROM,
> while we need to still permit sequential reads to the diagnostics
> EEPROM for atomicity reasons.
>
> 2) we need to relax the encoding check when we have no reported
> capabilities to allow 1000base-X based on the module bitrate.
>
> Thanks to Pali Rohár for responsive testing over the last two days.
>
> (Resending, dropping the utf-8 characters in Pali's name so the patches
> get through vger. Added Andrew's r-b tags.)
Series applied, thanks.
prev parent reply other threads:[~2020-12-10 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 11:21 [PATCH RESEND net-next 0/2] Add support for VSOL V2801F/CarlitoxxPro CPGOS03 GPON module Russell King - ARM Linux admin
2020-12-09 11:22 ` [PATCH net-next 1/2] net: sfp: VSOL V2801F / CarlitoxxPro CPGOS03-0490 v2.0 workaround Russell King
2020-12-09 11:22 ` [PATCH net-next 2/2] net: sfp: relax bitrate-derived mode check Russell King
2020-12-10 3:38 ` David Miller [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=20201209.193847.1853316342833410585.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pali@kernel.org \
/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).