From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] split phylink PCS operations and add PCS support for dpaa2
Date: Thu, 26 Mar 2020 15:14:58 +0000 [thread overview]
Message-ID: <20200326151458.GC25745@shell.armlinux.org.uk> (raw)
This series splits the phylink_mac_ops structure so that PCS can be
supported separately with their own PCS operations, separating them
from the MAC layer. This may need adaption later as more users come
along.
drivers/net/phy/phylink.c | 102 ++++++++++++++++++++++++++++++----------------
include/linux/phylink.h | 11 +++++
2 files changed, 78 insertions(+), 35 deletions(-)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
next reply other threads:[~2020-03-26 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:14 Russell King - ARM Linux admin [this message]
2020-03-26 15:15 ` [PATCH net-next 1/2] net: phylink: rename 'ops' to 'mac_ops' Russell King
2020-03-26 15:15 ` [PATCH net-next 2/2] net: phylink: add separate pcs operations structure Russell King
2020-03-26 21:49 ` Ioana Ciornei
2020-03-29 11:47 ` Russell King - ARM Linux admin
2020-03-29 15:10 ` Andrew Lunn
2020-03-26 15:19 ` [PATCH net-next 0/2] split phylink PCS operations and add PCS support for dpaa2 Russell King - ARM Linux admin
-- strict thread matches above, loose matches on Subject: below --
2020-03-17 14:49 [RFC " Russell King - ARM Linux admin
2020-03-26 15:14 ` [PATCH " Russell King - ARM Linux admin
2020-03-30 4:57 ` David Miller
2020-03-30 8:44 ` Russell King - ARM Linux admin
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=20200326151458.GC25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
/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).