From: Trent Piepho <tpiepho@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Sam Ravnborg <sam@ravnborg.org>,
jeff@garzik.org, John Rigby <jrigby@freescale.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] [Rev2] MPC5121 FEC support
Date: Tue, 17 Jun 2008 16:52:25 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0806171648300.7584@t2.domain.actdsltmp> (raw)
In-Reply-To: <485828B0.4010101@freescale.com>
On Tue, 17 Jun 2008, Scott Wood wrote:
> Sam Ravnborg wrote:
>> In general when you select a symbol that has dependencies you are almost
>> always on the wrong track.
>
> more specific options should make sure that they never select it when the
> dependencies aren't met.
Sure, in theory that would work, but in practice this ends up being a constant
source of broken builds.
>> Use a dependency here with a sane default - then people can set it to 'n'
>> if they really do not want this driver.
>>
>> Spreading selects too much is just causing you pain in the long run.
>
> I'm not sure I understand what you're looking for, but I don't see anything
> wrong with something like this (apart from missing help text):
>
> config FS_ENET
> bool
> select MII
> select PHYLIB
>
> config FS_ENET_HAS_SCC
> bool "Freescale CPM SCC Ethernet"
> depends on CPM1 || CPM2
> select FS_ENET
What prevents me from turning on FS_ENET_HAS_SCC without MII or PHYLIB? Why
is FS_ENET_HAS_SCC a bool, and not tristate?
next prev parent reply other threads:[~2008-06-17 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 19:08 [PATCH] [Rev2] MPC5121 FEC support John Rigby
2008-06-17 19:22 ` Sam Ravnborg
2008-06-17 19:31 ` Scott Wood
2008-06-17 19:46 ` Sam Ravnborg
2008-06-17 19:43 ` John Rigby
2008-06-17 19:57 ` Sam Ravnborg
2008-06-17 19:33 ` Scott Wood
2008-06-17 19:57 ` Sam Ravnborg
2008-06-17 20:03 ` Scott Wood
2008-06-17 21:00 ` Sam Ravnborg
2008-06-17 21:12 ` Scott Wood
2008-06-17 23:52 ` Trent Piepho [this message]
2008-06-18 5:00 ` Sam Ravnborg
2008-06-18 15:43 ` Scott Wood
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=Pine.LNX.4.64.0806171648300.7584@t2.domain.actdsltmp \
--to=tpiepho@freescale.com \
--cc=jeff@garzik.org \
--cc=jrigby@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=scottwood@freescale.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