All of lore.kernel.org
 help / color / mirror / Atom feed
From: github@bumblecito.com
To: Russell King <linux@armlinux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next v3 0/2] net: sfp: add ODI quirk and sort SFP quirk entries
Date: Wed, 18 Nov 2026 16:23:21 +0000	[thread overview]
Message-ID: <20261118162323.436219-1-github@bumblecito.com> (raw)

From: Israel Cueto <github@bumblecito.com>

This series adds 2500Base-X support for the ODI DFP-34X-2C3 XPON
SFP module and performs a cleanup of the SFP quirk table.

The first patch adds the ODI module quirk. The module was tested on
a Horaco ZX-SWTGW2C8F switch, establishing a 2500 Mb/s link with
speed and duplex forced and autonegotiation disabled.

The second patch is an independent table-ordering cleanup, sorting
the OEM and Turris entries without changing existing quirk behavior.

Thanks to Andrew Lunn for the suggestion to include the additional
ordering cleanup.

Israel Cueto (2):
  net: sfp: add 2500base-X quirk for ODI DFP-34X-2C3
  net: sfp: sort OEM and Turris SFP quirks

 drivers/net/phy/sfp.c | 37 ++++++++++++++++++++-----------------
 1 file changed, 20 insertions(+), 17 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-11-18 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 16:23 github [this message]
2026-11-18 16:23 ` [PATCH net-next v3 1/2] net: sfp: add 2500base-X quirk for ODI DFP-34X-2C3 github
2026-11-18 18:15   ` Andrew Lunn
     [not found]     ` <4fb66a63-b483-4777-9fe4-b94ccbe733b3@SynologyNAS>
2026-11-18 20:32       ` Andrew Lunn
2026-11-18 23:38   ` Andrew Lunn
2026-11-18 16:23 ` [PATCH net-next v3 2/2] net: sfp: sort OEM and Turris SFP quirks github
2026-11-18 18:11   ` Andrew Lunn

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=20261118162323.436219-1-github@bumblecito.com \
    --to=github@bumblecito.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --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 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.