From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/2] Rework tx fault fixups
Date: Fri, 06 Oct 2023 01:40:26 +0000 [thread overview]
Message-ID: <169655642605.20160.5177963742723021002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZRwYJXRizvkhm83M@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Oct 2023 14:33:25 +0100 you 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.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: sfp: re-implement ignoring the hardware TX_FAULT signal
https://git.kernel.org/netdev/net-next/c/e184e8609f8c
- [net-next,2/2] net: sfp: improve Nokia GPON sfp fixup
https://git.kernel.org/netdev/net-next/c/5ffe330e40bd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-06 1:40 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 ` [PATCH net-next 0/2] Rework tx fault fixups Russell King (Oracle)
2023-10-06 1:40 ` patchwork-bot+netdevbpf [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=169655642605.20160.5177963742723021002.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).