From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: lynxis@fe80.eu, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, axel@gembe.net,
Josh.Bendavid@cern.ch
Subject: Re: [PATCH net] net: pcs: pcs-mtk-lynxi: report in-band capability for 2500Base-X
Date: Thu, 22 Jan 2026 04:10:06 +0000 [thread overview]
Message-ID: <176905500636.1552379.14340282395835713572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b1cf26157b63fee838be09ae810497fb22fd8104.1768961746.git.daniel@makrotopia.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 02:23:17 +0000 you wrote:
> It turns out that 2500Base-X actually works fine with in-band status on
> MediaTek's LynxI PCS -- I wrongly concluded it didn't because it is
> broken in all the copper SFP modules and GPON sticks I used for testing.
>
> Hence report LINK_INBAND_ENABLE also for 2500Base-X mode.
>
> This reverts most of commit a003c38d9bbb ("net: pcs: pcs-mtk-lynxi:
> correctly report in-band status capabilities").
>
> [...]
Here is the summary with links:
- [net] net: pcs: pcs-mtk-lynxi: report in-band capability for 2500Base-X
https://git.kernel.org/netdev/net/c/e8ca461f7d19
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-01-22 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 2:23 [PATCH net] net: pcs: pcs-mtk-lynxi: report in-band capability for 2500Base-X Daniel Golle
2026-01-22 4:10 ` 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=176905500636.1552379.14340282395835713572.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Josh.Bendavid@cern.ch \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axel@gembe.net \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lynxis@fe80.eu \
--cc=matthias.bgg@gmail.com \
--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