From: patchwork-bot+netdevbpf@kernel.org
To: Birger Koblitz <mail@birger-koblitz.de>
Cc: linux@armlinux.org.uk, andrew@lunn.ch, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel@makrotopia.org
Subject: Re: [PATCH net-next] net: sfp: add quirk for 2.5G OEM BX SFP
Date: Fri, 21 Feb 2025 23:30:30 +0000 [thread overview]
Message-ID: <174018063000.2236176.16722302541554170478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250218-b4-lkmsub-v1-1-1e51dcabed90@birger-koblitz.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Feb 2025 18:59:40 +0100 you wrote:
> The OEM SFP-2.5G-BX10-D/U SFP module pair is meant to operate with
> 2500Base-X. However, in their EEPROM they incorrectly specify:
> Transceiver codes : 0x00 0x12 0x00 0x00 0x12 0x00 0x01 0x05 0x00
> BR, Nominal : 2500MBd
>
> Use sfp_quirk_2500basex for this module to allow 2500Base-X mode anyway.
> Tested on BananaPi R3.
>
> [...]
Here is the summary with links:
- [net-next] net: sfp: add quirk for 2.5G OEM BX SFP
https://git.kernel.org/netdev/net-next/c/a85035561025
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-21 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 17:59 [PATCH net-next] net: sfp: add quirk for 2.5G OEM BX SFP Birger Koblitz
2025-02-21 23:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 6:29 Birger Koblitz
2025-02-18 1:00 ` Jakub Kicinski
2025-02-12 15:13 Birger Koblitz
2025-02-14 21:24 ` Jakub Kicinski
2025-02-09 11:01 Birger Koblitz
2025-02-09 15:13 ` Daniel Golle
2025-02-12 3:02 ` Jakub Kicinski
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=174018063000.2236176.16722302541554170478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mail@birger-koblitz.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.