From: arigead@gmail.com (John Whitmore)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why do some config options return limited info from a search?
Date: Tue, 20 Mar 2018 21:19:59 +0000 [thread overview]
Message-ID: <20180320211957.GA8772@bamboo> (raw)
In-Reply-To: <168576.1521420592@turing-police.cc.vt.edu>
On Sun, Mar 18, 2018 at 08:49:52PM -0400, valdis.kletnieks at vt.edu wrote:
> On Mon, 19 Mar 2018 00:08:10 -0000, John Whitmore said:
>
> > Sometimes however you get a module which don't give this information. Is this
> > intentional, signify something, or just an oversight for that config option?
> > For example SND_HDA_CORE:
>
> > Symbol: SND_HDA_CORE [=m]
> > Type : tristate
> > Defined at sound/hda/Kconfig:1
> > Depends on: SOUND [=y] && !UML && SND [=y]
> > Selects: REGMAP [=y]
> > Selected by:
> > - SND_HDA_EXT_CORE [=m] && SOUND [=y] && !UML && SND [=y]
> > - SND_HDA [=m] && SOUND [=y] && !UML && SND [=y]
>
> Some internal symbols don't have any visible menu-selects, because they are
> intended to be turned on only via other things doing 'SELECT'. After all,
> SND_HDA_CORE has little to no reason to be enabled unless your kernel build
> config asks for SND_HDA or SND_HDA_EXT_CORE (and *that* symbol is 'm', which is
> why SND_HDA_CORE is also ''m'. Switching EXT_CORE to 'y' will then auto-switch
> this one to 'y' as well).
>
Perfectly logical and simple. Thanks for your answer that now all makes sense.
prev parent reply other threads:[~2018-03-20 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 0:08 Why do some config options return limited info from a search? John Whitmore
2018-03-19 0:49 ` valdis.kletnieks at vt.edu
2018-03-20 21:19 ` John Whitmore [this message]
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=20180320211957.GA8772@bamboo \
--to=arigead@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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).