From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: how can default Kconfig values be defined elsewhere?
Date: Tue, 30 Jul 2019 10:22:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1907301018400.21476@localhost.localdomain> (raw)
another kbuild-related question -- from kconfig-language.rst:
- default value: "default" <expr> ["if" <expr>]
A config option can have any number of default values. If multiple
default values are visible, only the first defined one is active.
Default values are not limited to the menu entry where they are
defined. This means the default can be defined somewhere else or be
overridden by an earlier definition.
wait ... default values can be defined elsewhere from the menu entry
for which that default is to be set? i was unaware of this; can
someone provide an example? or am i misreading this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-07-30 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 14:22 Robert P. J. Day [this message]
2019-07-30 14:53 ` how can default Kconfig values be defined elsewhere? KingLotterry
2019-07-30 17:53 ` Robert P. J. Day
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=alpine.LFD.2.21.1907301018400.21476@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@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 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.