From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: <linux@armlinux.org.uk>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>, <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Ong Boon Leong <boon.leong.ong@intel.com>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH net-next] net: pcs: xpcs: depends on PHYLINK in Kconfig
Date: Wed, 22 Jun 2022 16:12:29 -0700 [thread overview]
Message-ID: <20220622161229.3a08de6b@kernel.org> (raw)
In-Reply-To: <cebed632d3337a40cedbf3da78ff1e1154b1ae3a.camel@redhat.com>
On Wed, 22 Jun 2022 17:42:13 +0200 Paolo Abeni wrote:
> @Jakub: please let me know if you prefer to go ahead yourself, or me
> sending a v3 with 'depends PHYLINK' + the above (or any other option ;)
[resending, sorry, Russell let me know that my MUA broke the headers]
Well, IDK. You said "depends PHYLINK" which makes me feel like I
haven't convinced you at all :) Unless you mean add the dependency
on the consumers not on PCS_XPCS itself, but that's awkward.
What I was saying is that "depends" in a symbol which is only
"select"ed by other symbols makes no sense. IIUC "select" does not
visit dependencies, so putting "depends" on an user-invisible symbol
(i.e. symbol without a prompt) achieves nothing.
So PCS_XPCS can have no "depends" if we hide it.
The way I see it - PHYLINK already selects MDIO_DEVICE. So we can drop
the MDIO business from PCS_XPCS, add "select PHYLINK", hide it by
removing the prompt, and we're good. Then again, I admit I have not
tested this at all so I could be speaking gibberish...
diff --git a/drivers/net/pcs/Kconfig b/drivers/net/pcs/Kconfig
index 22ba7b0b476d..f778e5155fae 100644
--- a/drivers/net/pcs/Kconfig
+++ b/drivers/net/pcs/Kconfig
@@ -6,8 +6,8 @@
menu "PCS device drivers"
config PCS_XPCS
- tristate "Synopsys DesignWare XPCS controller"
- depends on MDIO_DEVICE && MDIO_BUS
+ tristate
+ select PHYLINK
help
This module provides helper functions for Synopsys DesignWare XPCS
next prev parent reply other threads:[~2022-06-22 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 7:55 [PATCH net-next] net: pcs: xpcs: depends on PHYLINK in Kconfig 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 [this message]
2022-06-23 14:00 ` Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 20:29 Jakub Kicinski
2022-06-25 6:00 ` 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=20220622161229.3a08de6b@kernel.org \
--to=kuba@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=linux@armlinux.org.uk \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).