From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>, Heiner Kallweit <hkallweit1@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Jakub Kicinski <kuba@kernel.org>,
Jose Abreu <Jose.Abreu@synopsys.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: [PATCH net-next 0/3] Remove phylink_state's an_enabled member
Date: Tue, 21 Mar 2023 15:57:31 +0000 [thread overview]
Message-ID: <ZBnT6yW9UY1sAsiy@shell.armlinux.org.uk> (raw)
Hi,
Now that all the fixes and correctness patches have been merged, it is
time to switch the two users that make use of .an_enabled to check the
Autoneg bit in the advertising mask, and finally remove the
.an_enabled member.
The first two patches remove the last uses of .an_enabled, which are
in DPAA2 and XPCS. The final patch removes the member.
drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c | 3 +-
drivers/net/pcs/pcs-xpcs.c | 10 +++++--
drivers/net/phy/phylink.c | 37 +++++++++++-------------
include/linux/phylink.h | 2 --
4 files changed, 26 insertions(+), 26 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next reply other threads:[~2023-03-21 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 15:57 Russell King (Oracle) [this message]
2023-03-21 15:58 ` [PATCH net-next 1/3] net: dpaa2-mac: use Autoneg bit rather than an_enabled Russell King (Oracle)
2023-03-22 15:46 ` Simon Horman
2023-03-21 15:58 ` [PATCH net-next 2/3] net: pcs: xpcs: " Russell King (Oracle)
2023-03-22 15:47 ` Simon Horman
2023-03-21 15:58 ` [PATCH net-next 3/3] net: phylink: remove an_enabled Russell King (Oracle)
2023-03-22 16:51 ` Simon Horman
2023-03-23 5:50 ` [PATCH net-next 0/3] Remove phylink_state's an_enabled member patchwork-bot+netdevbpf
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=ZBnT6yW9UY1sAsiy@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.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).