From: Tony Lindgren <tony@atomide.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: davem@davemloft.net, mugunthanvnm@ti.com,
prabhakar.csengg@gmail.com, varkabhadram@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
grygorii.strashko@ti.com, lokeshvutla@ti.com, mpa@pengutronix.de,
w-kwok2@ti.com
Subject: Re: [PATCH net-next 2/2] net: netcp: select davinci_mdio driver by default
Date: Mon, 2 Mar 2015 16:04:45 -0800 [thread overview]
Message-ID: <20150303000444.GC3756@atomide.com> (raw)
In-Reply-To: <54F4DA06.9070505@ti.com>
* Murali Karicheri <m-karicheri2@ti.com> [150302 13:49]:
> On 03/02/2015 11:11 AM, Tony Lindgren wrote:
> >
> >Because we are now force selecting items that may have other
> >dependencies later on that will not be satisfied. That causes
> >all kinds of make randconfig build errors.
> >
> My mistake. I didn't ask you what is your definition of a silent option? An
> option not selected by any other option? Or an option for which default
> value not defined? Can you clarify this so that I can make sense of your
> comment? I checked Documentation/kbuild/kconfig.txt as well as
> Documentation/kbuild/kconfig-language.txt for defintion, but can't find it.
>
> Howeve, I read the warning about using "select" in the above document since
> it blindly select the option without checking dependencies. So AFAIK, select
> becomes an issue if the config option is not the leaf option of the config
> tree as the dependency checking is not in place and can cause issues. In
> this case it is safe as DAVINCI_MDIO is a leaf option and only selects
> PHYLIB which dependents on NETDEVICES and we know this is true for NETCP
> devices. So select is just fine here.
OK I think you're right that in this case it won't cause issues.
But if these cpsw components are never selectable by the user for
any real use case, then you may want to make them silent Kconfig
options:
config TI_DAVINCI_MDIO
bool
select PHYLIB
config TI_DAVINCI_CPDMA
bool
config TI_CPSW_PHY_SEL
bool
config TI_CPSW_ALE
bool
...
Regards,
Tony
next prev parent reply other threads:[~2015-03-03 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:27 [PATCH net-next 1/2] net: davinci_mdio: don't request io address range Murali Karicheri
2015-02-24 21:27 ` [PATCH net-next 2/2] net: netcp: select davinci_mdio driver by default Murali Karicheri
2015-02-27 16:29 ` Tony Lindgren
2015-02-27 20:56 ` Murali Karicheri
2015-03-02 16:11 ` Tony Lindgren
2015-03-02 21:45 ` Murali Karicheri
2015-03-03 0:04 ` Tony Lindgren [this message]
2015-03-11 16:18 ` Murali Karicheri
2015-02-27 15:55 ` [PATCH net-next 1/2] net: davinci_mdio: don't request io address range Lad, Prabhakar
2015-02-27 16:51 ` Tony Lindgren
2015-03-11 16:35 ` Murali Karicheri
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=20150303000444.GC3756@atomide.com \
--to=tony@atomide.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=m-karicheri2@ti.com \
--cc=mpa@pengutronix.de \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=varkabhadram@gmail.com \
--cc=w-kwok2@ti.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).