From: patchwork-bot+netdevbpf@kernel.org
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.ch, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, linux@armlinux.org.uk, f.fainelli@gmail.com,
hkallweit1@gmail.com, corbet@lwn.net
Subject: Re: [PATCH net-next v3 0/2] doc: sfp-phylink: update the porting guide
Date: Thu, 07 Mar 2024 14:30:28 +0000 [thread overview]
Message-ID: <170982182883.31331.10062654411732852553.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301164309.3643849-1-maxime.chevallier@bootlin.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 1 Mar 2024 17:43:06 +0100 you wrote:
> Hello everyone,
>
> Here's a V3 for an update on the phylink porting guide. The only
> difference with V2 is a whitespace fix along with a line-wrap.
>
> The main point of the update is the description of a basic process to
> follow to expose one or more PCS to phylink. Let me know if you spot any
> inaccuracies in the guide.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] doc: sfp-phylink: update the porting guide with PCS handling
https://git.kernel.org/netdev/net-next/c/9b1d8588397a
- [net-next,v3,2/2] net: phylink: clean the pcs_get_state documentation
https://git.kernel.org/netdev/net-next/c/68ac1e46425c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-07 14:30 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
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 ` patchwork-bot+netdevbpf [this message]
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=170982182883.31331.10062654411732852553.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=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