From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, 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>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH net-next 2/2] doc: sfp-phylink: mention the mac_capabilities and supported_interfaces
Date: Mon, 26 Feb 2024 11:45:03 +0000 [thread overview]
Message-ID: <Zdx5v1UXDqsKsjW8@shell.armlinux.org.uk> (raw)
In-Reply-To: <20240220160406.3363002-3-maxime.chevallier@bootlin.com>
On Tue, Feb 20, 2024 at 05:04:04PM +0100, Maxime Chevallier wrote:
> + Fill-in all the :c:type:`phy_interface_t <phy_interface_t>` (i.e. all MAC to
> + PHY link modes) that your MAC can output. The following example shows a
Technically, this should be "MAC and all PCS associated with this MAC".
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-02-26 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:04 [PATCH net-next 0/2] doc: sfp-phylink: update the porting guide Maxime Chevallier
2024-02-20 16:04 ` [PATCH net-next 1/2] doc: sfp-phylink: drop the mention to phylink_config->pcs_poll Maxime Chevallier
2024-02-26 11:41 ` Russell King (Oracle)
2024-02-26 15:02 ` Maxime Chevallier
2024-02-20 16:04 ` [PATCH net-next 2/2] doc: sfp-phylink: mention the mac_capabilities and supported_interfaces Maxime Chevallier
2024-02-26 11:45 ` Russell King (Oracle) [this message]
2024-02-26 15:07 ` Maxime Chevallier
2024-02-26 11:01 ` [PATCH net-next 0/2] doc: sfp-phylink: update the porting guide 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=Zdx5v1UXDqsKsjW8@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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=maxime.chevallier@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).