From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: enachman@marvell.com, tchornyi@marvell.com, vmytnyk@marvell.com,
vkochan@marvell.com, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, alok.a.tiwarilinux@gmail.com
Subject: Re: [PATCH v2 net-next] net: marvell: prestera: fix FEC error message for SFP ports
Date: Sat, 07 Feb 2026 04:20:24 +0000 [thread overview]
Message-ID: <177043802432.1183264.5861615136442702273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260205091958.231413-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Feb 2026 01:19:55 -0800 you wrote:
> In prestera_ethtool_set_fecparam(), the error message is opposite of
> the condition checking PRESTERA_PORT_TCVR_SFP. FEC configuration is
> not allowed on SFP ports, but the message says "non-SFP ports", which
> does not match the condition. However, FEC may be required depending on
> the transceiver, cable, or mode, and firmware already validates invalid
> combinations.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: marvell: prestera: fix FEC error message for SFP ports
https://git.kernel.org/netdev/net-next/c/dddb0198c2a8
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:[~2026-02-07 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 9:19 [PATCH v2 net-next] net: marvell: prestera: fix FEC error message for SFP ports Alok Tiwari
2026-02-05 10:49 ` [EXTERNAL] " Elad Nachman
2026-02-07 4:20 ` 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=177043802432.1183264.5861615136442702273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=alok.a.tiwarilinux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enachman@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tchornyi@marvell.com \
--cc=vkochan@marvell.com \
--cc=vmytnyk@marvell.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