From: "Marek Behún" <kabel@kernel.org>
To: netdev@vger.kernel.org,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
davem@davemloft.net, kuba@kernel.org
Cc: pavana.sharma@digi.com, vivien.didelot@gmail.com,
f.fainelli@gmail.com, lkp@intel.com, ashkan.boldaji@digi.com,
andrew@lunn.ch,
"Chris Packham" <chris.packham@alliedtelesis.co.nz>,
olteanv@gmail.com, "Marek Behún" <kabel@kernel.org>
Subject: [PATCH net-next 0/4] Add 5gbase-r PHY interface mode
Date: Tue, 16 Feb 2021 20:20:51 +0100 [thread overview]
Message-ID: <20210216192055.7078-1-kabel@kernel.org> (raw)
Hello,
there is still some testing needed for Amethyst patches, so I have
split the part adding support for 5gbase-r interface mode and am sending
it alone.
The first two patches are already reviewed.
Changes since last patches (Amethyst v16):
- added phylink 5gbase-r handler
- added SFP support for 5gbase-r mode
Marek
Marek Behún (2):
net: phylink: Add 5gbase-r support
sfp: add support for 5gbase-t SFPs
Pavana Sharma (2):
dt-bindings: net: Add 5GBASER phy interface
net: phy: Add 5GBASER interface mode
.../devicetree/bindings/net/ethernet-controller.yaml | 1 +
Documentation/networking/phy.rst | 6 ++++++
drivers/net/phy/phylink.c | 4 ++++
drivers/net/phy/sfp-bus.c | 3 +++
include/linux/phy.h | 4 ++++
5 files changed, 18 insertions(+)
--
2.26.2
next reply other threads:[~2021-02-16 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 19:20 Marek Behún [this message]
2021-02-16 19:20 ` [PATCH net-next 1/4] dt-bindings: net: Add 5GBASER phy interface Marek Behún
2021-02-16 19:20 ` [PATCH net-next 2/4] net: phy: Add 5GBASER interface mode Marek Behún
2021-02-16 19:20 ` [PATCH net-next 3/4] net: phylink: Add 5gbase-r support Marek Behún
2021-02-16 19:20 ` [PATCH net-next 4/4] sfp: add support for 5gbase-t SFPs Marek Behún
2021-02-16 22:20 ` [PATCH net-next 0/4] Add 5gbase-r PHY interface mode 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=20210216192055.7078-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=ashkan.boldaji@digi.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pavana.sharma@digi.com \
--cc=vivien.didelot@gmail.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).