From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, lkp@intel.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk,
rmk+kernel@armlinux.org.uk, boon.leong.ong@intel.com
Subject: Re: [PATCH net-next] net: pcs: xpcs: depends on PHYLINK in Kconfig
Date: Sat, 25 Jun 2022 06:00:14 +0000 [thread overview]
Message-ID: <165613681433.10048.1576945052531169096.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220623202933.2341938-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Jun 2022 13:29:33 -0700 you wrote:
> This is yet another attempt at fixing:
>
> >> ERROR: modpost: "phylink_mii_c22_pcs_encode_advertisement" [drivers/net/pcs/pcs_xpcs.ko] undefined!
> >> ERROR: modpost: "phylink_mii_c22_pcs_decode_state" [drivers/net/pcs/pcs_xpcs.ko] undefined!
>
> Switch XPCS to be invisible, as Russell points out it's
> "selected" by its consumers. Drop the dependency on MDIO_BUS
> as "depends" is meaningless on "selected" symbols.
>
> [...]
Here is the summary with links:
- [net-next] net: pcs: xpcs: depends on PHYLINK in Kconfig
https://git.kernel.org/netdev/net-next/c/ebeae54d3a77
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:[~2022-06-25 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 20:29 [PATCH net-next] net: pcs: xpcs: depends on PHYLINK in Kconfig Jakub Kicinski
2022-06-25 6:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-21 7:55 Paolo Abeni
2022-06-21 19:50 ` Jakub Kicinski
2022-06-22 13:50 ` Paolo Abeni
2022-06-22 14:15 ` Russell King (Oracle)
2022-06-22 15:35 ` Jakub Kicinski
2022-06-22 15:42 ` Paolo Abeni
2022-06-22 23:12 ` Jakub Kicinski
2022-06-23 14:00 ` Paolo Abeni
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=165613681433.10048.1576945052531169096.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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).