From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: davem@davemloft.net
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH net-next v2 0/2] doc: sfp-phylink: update the porting guide
Date: Wed, 28 Feb 2024 10:57:52 +0100 [thread overview]
Message-ID: <20240228095755.1499577-1-maxime.chevallier@bootlin.com> (raw)
Hello everyone,
This small series updates the Phylink porting guide, mentionning PCS
handling, suported_interfaces and mac_capabilities.
The first patch is related to the dedicated documentation, whil the
second patch fixes a small discrepancy in the phylink code
documentation.
Link to V1: https://lore.kernel.org/netdev/20240220160406.3363002-1-maxime.chevallier@bootlin.com/
Maxime Chevallier (2):
doc: sfp-phylink: update the porting guide with PCS handling
net: phylink: clean the pcs_get_state documentation
Documentation/networking/sfp-phylink.rst | 146 ++++++++++++++++++++---
include/linux/phylink.h | 3 -
2 files changed, 132 insertions(+), 17 deletions(-)
--
2.43.2
next reply other threads:[~2024-02-28 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 9:57 Maxime Chevallier [this message]
2024-02-28 9:57 ` [PATCH net-next v2 1/2] doc: sfp-phylink: update the porting guide with PCS handling Maxime Chevallier
2024-02-29 3:56 ` Jakub Kicinski
2024-02-28 9:57 ` [PATCH net-next v2 2/2] net: phylink: clean the pcs_get_state documentation Maxime Chevallier
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=20240228095755.1499577-1-maxime.chevallier@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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
all inboxes | Powered by JetHome®