From: Andrew Lunn <andrew@lunn.ch>
To: github@bumblecito.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v2] net: sfp: add 2500base-X quirk for ODI DFP-34X-2C3
Date: Wed, 18 Nov 2026 14:35:02 +0100 [thread overview]
Message-ID: <238e2188-9460-4092-9cdd-77e17554a3d2@lunn.ch> (raw)
In-Reply-To: <20261118034510.434732-1-github@bumblecito.com>
On Wed, Nov 18, 2026 at 03:45:10AM +0000, github@bumblecito.com wrote:
> From: Israel Cueto <github@bumblecito.com>
>
> The ODI DFP-34X-2C3 XPON SFP module supports 2500Base-X.
>
> Add a quirk to enable 2500Base-X support for this module.
>
> Tested on a Horaco ZX-SWTGW2C8F switch with an ODI
> DFP-34X-2C3 module. A 2500 Mb/s link was established
> with speed and duplex forced and autonegotiation disabled.
>
> Signed-off-by: Israel Cueto <github@bumblecito.com>
> ---
> Changes in v2:
> - Move the ODI quirk to its alphabetical position.
Thanks for trying to keep the list somewhat sorted. However, you need
to start a new thread for every new version of the patch.
If you have time, could you add a second patch and move OEM and Turris
into order? Not required to get this patch merged, just nice to have.
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2026-11-18 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 2:56 [PATCH net-next] " github
2026-11-18 3:28 ` Jakub Kicinski
2026-11-18 3:45 ` [PATCH net-next v2] " github
2026-11-18 13:35 ` Andrew Lunn [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=238e2188-9460-4092-9cdd-77e17554a3d2@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=github@bumblecito.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®