From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, hkallweit1@gmail.com, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [net-next PATCH v3 02/10] net: phy: Rename MDIO_CTRL1_SPEED for 2.5G and 5G to reflect PMA values
Date: Wed, 12 Nov 2025 10:42:06 +0000 [thread overview]
Message-ID: <aRRkfg6zKW5gAOz6@shell.armlinux.org.uk> (raw)
In-Reply-To: <176279047080.2130772.6017646787024578804.stgit@ahduyck-xeon-server.home.arpa>
On Mon, Nov 10, 2025 at 08:01:10AM -0800, Alexander Duyck wrote:
> From: Alexander Duyck <alexanderduyck@fb.com>
>
> The 2.5G and 5G values are not consistent between the PCS CTRL1 and PMA
> CTRL1 values. In order to avoid confusion between the two I am updating the
> values to include "PMA" in the name similar to values used in similar
> places.
As this us UAPI, please _add_ new values with _PCS_ and _PMA_ infixes
rather than renaming existing definitionsi.
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-11-12 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 16:00 [net-next PATCH v3 00/10] net: phy: Add support for fbnic PHY w/ 25G, 50G, and 100G support Alexander Duyck
2025-11-10 16:00 ` [net-next PATCH v3 01/10] net: phy: Add support for 25, 50 and 100Gbps PMA to genphy_c45_read_pma Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 02/10] net: phy: Rename MDIO_CTRL1_SPEED for 2.5G and 5G to reflect PMA values Alexander Duyck
2025-11-12 8:53 ` Maxime Chevallier
2025-11-12 10:42 ` Russell King (Oracle) [this message]
2025-11-12 16:32 ` Alexander H Duyck
2025-11-10 16:01 ` [net-next PATCH v3 03/10] net: pcs: xpcs: Add support for 25G, 50G, and 100G interfaces Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 04/10] net: pcs: xpcs: Fix PMA identifier handling in XPCS Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 05/10] net: pcs: xpcs: Add support for FBNIC 25G, 50G, 100G PMA Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 06/10] fbnic: Rename PCS IRQ to MAC IRQ as it is actually a MAC interrupt Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 07/10] fbnic: Add logic to track PMD state via MAC/PCS signals Alexander Duyck
2025-11-10 16:01 ` [net-next PATCH v3 08/10] fbnic: Cleanup handling for link down event statistics Alexander Duyck
2025-11-10 16:02 ` [net-next PATCH v3 09/10] fbnic: Add SW shim for MDIO interface to PMA/PMD and PCS Alexander Duyck
2025-11-10 16:02 ` [net-next PATCH v3 10/10] fbnic: Replace use of internal PCS w/ Designware XPCS Alexander Duyck
2025-11-11 14:23 ` [net-next PATCH v3 00/10] net: phy: Add support for fbnic PHY w/ 25G, 50G, and 100G support Paolo Abeni
2025-11-11 15:23 ` Jakub Kicinski
2025-11-11 16:09 ` Alexander Duyck
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=aRRkfg6zKW5gAOz6@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexander.duyck@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).