From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Tim Harvey <tharvey@gateworks.com>,
Vladimir Oltean <olteanv@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v3 2/3] net: mdio: Update speed register bits
Date: Fri, 2 Dec 2022 19:00:57 +0000 [thread overview]
Message-ID: <Y4pLaQ4EB5jSuX5d@shell.armlinux.org.uk> (raw)
In-Reply-To: <20221202181719.1068869-3-sean.anderson@seco.com>
On Fri, Dec 02, 2022 at 01:17:17PM -0500, Sean Anderson wrote:
> This updates the speed register bits to the 2018 revision of 802.3. It
> also splits up the definitions to prevent confusion in casual observers.
Are you going to do it for the other registers so that there is
consistency?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-12-02 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:17 [PATCH net-next v3 0/3] phy: aquantia: Determine rate adaptation support from registers Sean Anderson
2022-12-02 18:17 ` [PATCH net-next v3 1/3] net: phy: Move/rename phylink_interface_max_speed Sean Anderson
2022-12-02 19:00 ` Russell King (Oracle)
2022-12-02 18:17 ` [PATCH net-next v3 2/3] net: mdio: Update speed register bits Sean Anderson
2022-12-02 19:00 ` Russell King (Oracle) [this message]
2022-12-02 19:15 ` Sean Anderson
2022-12-02 18:17 ` [PATCH net-next v3 3/3] phy: aquantia: Determine rate adaptation support from registers Sean Anderson
2022-12-03 5:26 ` 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=Y4pLaQ4EB5jSuX5d@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.com \
--cc=tharvey@gateworks.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.