From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, "Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH net-next 0/2] Add support for VSOL V2801F/CarlitoxxPro CPGOS03 GPON module
Date: Wed, 9 Dec 2020 11:17:32 +0000 [thread overview]
Message-ID: <20201209111732.GL1605@shell.armlinux.org.uk> (raw)
In-Reply-To: <20201209111109.GR1551@shell.armlinux.org.uk>
Oh, it's because Pali Rohar's name contains UTF-8 and I can't
encode that prior to sending the actual patches themselves.
Sorry, I'm going to have to have to limit to ASCII only in the
header lines when mailing list patches - scripting the encoding
for UTF-8 characters in shell is far from simple.
On Wed, Dec 09, 2020 at 11:11:09AM +0000, Russell King - ARM Linux admin wrote:
> Jakub,
>
> What's happening with these patches?
>
> If I'm getting the patchwork URLs correct, these patches seem not to
> appear in patchwork. They both went to netdev as normal and where
> accepted by vger from what I can see.
>
> Thanks.
>
> On Fri, Dec 04, 2020 at 02:34:52PM +0000, Russell King - ARM Linux admin wrote:
> > 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.
> >
> > drivers/net/phy/sfp-bus.c | 11 ++++-----
> > drivers/net/phy/sfp.c | 63 +++++++++++++++++++++++++++++++++++++++++++----
> > 2 files changed, 63 insertions(+), 11 deletions(-)
> >
> > --
> > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
> >
>
> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2020-12-09 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 14:34 [PATCH net-next 0/2] Add support for VSOL V2801F/CarlitoxxPro CPGOS03 GPON module Russell King - ARM Linux admin
[not found] ` <E1klCB8-0001sW-Ma@rmk-PC.armlinux.org.uk>
2020-12-04 15:00 ` [PATCH net-next 1/2] net: sfp: VSOL V2801F / CarlitoxxPro CPGOS03-0490 v2.0 workaround Russell King - ARM Linux admin
2020-12-04 15:31 ` Andrew Lunn
2020-12-09 11:20 ` Russell King - ARM Linux admin
[not found] ` <E1klCBD-0001si-Qj@rmk-PC.armlinux.org.uk>
2020-12-04 15:38 ` [PATCH net-next 2/2] net: sfp: relax bitrate-derived mode check Andrew Lunn
2020-12-04 15:51 ` Russell King - ARM Linux admin
2020-12-09 11:11 ` [PATCH net-next 0/2] Add support for VSOL V2801F/CarlitoxxPro CPGOS03 GPON module Russell King - ARM Linux admin
2020-12-09 11:17 ` Russell King - ARM Linux admin [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=20201209111732.GL1605@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--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).