From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: [info] Kconfig SELECT statement rules - was: FIXED_PHY is broken...
Date: Tue, 16 Dec 2014 17:36:45 +0100 [thread overview]
Message-ID: <54905F9D.2090208@hartkopp.net> (raw)
In-Reply-To: <20141216.112534.1684849738404064350.davem@davemloft.net>
Just a hint from Dave when the SELECT statement is not appropriate when
creating Kconfig files ... ;-)
Regards,
Oliver
-------- Forwarded Message --------
Subject: FIXED_PHY is broken...
Date: Tue, 16 Dec 2014 11:25:34 -0500 (EST)
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
CC: f.fainelli@gmail.com
I get this now when I run oldconfig:
warning: (NET_DSA_BCM_SF2 && BCMGENET && SYSTEMPORT) selects FIXED_PHY which
has unmet direct dependencies (NETDEVICES && PHYLIB=y)
For the thousandth time, you cannot select Kconfig options which have
dependencies of any kind, because select does not recursively cause
dependencies to be enabled up to the root of the Kconfig tree.
If you select on something which has a "depends on", stop right there
because you can't do it.
It only works for pure leaf Kconfig nodes with no deps.
All you needed to do in order to test this was do an allmodconfig
build.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-16 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 16:25 FIXED_PHY is broken David Miller
2014-12-16 16:36 ` Oliver Hartkopp [this message]
2014-12-16 19:30 ` David Miller
2014-12-16 20:15 ` David Miller
2014-12-16 20:23 ` Florian Fainelli
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=54905F9D.2090208@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.