mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>, davem@davemloft.net
Cc: 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>,
	Russell King <linux@armlinux.org.uk>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH net-next v3 1/2] doc: sfp-phylink: update the porting guide with PCS handling
Date: Thu, 07 Mar 2024 11:48:06 +0100	[thread overview]
Message-ID: <f44c6961c6585711d72c59da971c17d26c54c7da.camel@redhat.com> (raw)
In-Reply-To: <20240301164309.3643849-2-maxime.chevallier@bootlin.com>

On Fri, 2024-03-01 at 17:43 +0100, Maxime Chevallier wrote:
> Now that phylink has a comprehensive PCS support, update the porting
> guide to explain the process of supporting the PCS configuration. This
> also removed outdated references to phylink_config fields that no longer
> exists.
> 
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>

FTR, this looks sane to me, and I think we should merge the series,
unless someone from the phy crew bark soon ;)

Thanks,

Paolo


  reply	other threads:[~2024-03-07 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 16:43 [PATCH net-next v3 0/2] doc: sfp-phylink: update the porting guide Maxime Chevallier
2024-03-01 16:43 ` [PATCH net-next v3 1/2] doc: sfp-phylink: update the porting guide with PCS handling Maxime Chevallier
2024-03-07 10:48   ` Paolo Abeni [this message]
2024-03-01 16:43 ` [PATCH net-next v3 2/2] net: phylink: clean the pcs_get_state documentation Maxime Chevallier
2024-03-07 14:30 ` [PATCH net-next v3 0/2] doc: sfp-phylink: update the porting guide 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=f44c6961c6585711d72c59da971c17d26c54c7da.camel@redhat.com \
    --to=pabeni@redhat.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=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --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®