From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Christian Marangi <ansuelsmth@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 0/2] Rework tx fault fixups
Date: Thu, 5 Oct 2023 18:47:15 +0100 [thread overview]
Message-ID: <ZR72oxHqdiVCIX3i@shell.armlinux.org.uk> (raw)
In-Reply-To: <ZRwYJXRizvkhm83M@shell.armlinux.org.uk>
On Tue, Oct 03, 2023 at 02:33:25PM +0100, Russell King (Oracle) wrote:
> Hi,
>
> This series reworks the tx-fault fixup and then improves the Nokia GPON
> workaround to also ignore the RX LOS signal as well. We do this by
> introducing a mask of hardware pin states that should be ignored,
> converting the tx-fault fixup to use that, and then augmenting it for
> RX LOS.
>
> drivers/net/phy/sfp.c | 33 ++++++++++++++++++++++++---------
> 1 file changed, 24 insertions(+), 9 deletions(-)
FYI, Christian has provided a tested-by:
Tested-by: Christian Marangi <ansuelsmth@gmail.com>
Thanks!
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2023-10-05 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 13:33 [PATCH net-next 0/2] Rework tx fault fixups Russell King (Oracle)
2023-10-03 13:34 ` [PATCH net-next 1/2] net: sfp: re-implement ignoring the hardware TX_FAULT signal Russell King (Oracle)
2023-10-03 13:34 ` [PATCH net-next 2/2] net: sfp: improve Nokia GPON sfp fixup Russell King (Oracle)
2023-10-05 17:47 ` Russell King (Oracle) [this message]
2023-10-06 1:40 ` [PATCH net-next 0/2] Rework tx fault fixups patchwork-bot+netdevbpf
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=ZR72oxHqdiVCIX3i@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).