[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230425145719.621d6568@kernel.org>
Date: Tue, 25 Apr 2023 14:57:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: "Paolo Abeni" <pabeni@...hat.com>, Netdev <netdev@...r.kernel.org>,
"Andrew Lunn" <andrew@...n.ch>,
"Heiner Kallweit" <hkallweit1@...il.com>,
"Russell King" <linux@...linux.org.uk>,
"David S . Miller" <davem@...emloft.net>,
"Eric Dumazet" <edumazet@...gle.com>
Subject: Re: [PATCH net-next] net: phy: drop PHYLIB_LEDS knob
On Tue, 25 Apr 2023 22:35:46 +0100 Arnd Bergmann wrote:
> > @Andrew, @Arnd: the rationale here is to avoid the new config knob=y,
> > which caused in the past a few complains from Linus. In this case I
> > think the raised exception is not valid, for the reason mentioned above.
> >
> > If you have different preferences or better solutions to address that,
> > please voice them :)
>
> I think using IS_REACHABLE() is generally much worse than having another
> explicit option, because it makes it harder for users to figure out why
> something does not work as they had expected it to.
>
> Note that I'm the one who introduced IS_REACHABLE() to start with,
> but the intention at the time was really to replace open-coded
> logic doing the same thing, not to have it as a generic way to
> hide broken dependencies.
Agreed :( But that kind of presupposed that user knows what they
are looking for, right?
My thinking was this: using "depends on" instead and preventing
the bad configuration from occurring is a strongly preferred
alternative to IS_REACHABLE(). But an extra third option which will
be hidden from nconfig will not prevent user from doing LEDS=m PHYS=y.
Powered by blists - more mailing lists