From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk
Subject: Re: [PATCH net-next] net: phylink: reimplement population of pl->supported for in-band
Date: Sun, 17 Dec 2023 01:11:52 +0000 [thread overview]
Message-ID: <170277551252.21831.11174233431443095768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213155142.380779-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 13 Dec 2023 17:51:42 +0200 you wrote:
> phylink_parse_mode() populates all possible supported link modes for a
> given phy_interface_t, for the case where a phylib phy may be absent and
> we can't retrieve the supported link modes from that.
>
> Russell points out that since the introduction of the generic validation
> helpers phylink_get_capabilities() and phylink_caps_to_linkmodes(), we
> can rewrite this procedure to populate the pl->supported mask, so that
> instead of spelling out the link modes, we derive an intermediary
> mac_capabilities bit field, and we convert that to the equivalent link
> modes.
>
> [...]
Here is the summary with links:
- [net-next] net: phylink: reimplement population of pl->supported for in-band
https://git.kernel.org/netdev/net-next/c/37a8997fc5a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-17 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 15:51 [PATCH net-next] net: phylink: reimplement population of pl->supported for in-band Vladimir Oltean
2023-12-17 1:11 ` patchwork-bot+netdevbpf [this message]
2023-12-17 10:39 ` Russell King (Oracle)
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=170277551252.21831.11174233431443095768.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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).