From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: clarifying details about "is not set" lines in kernel config fragment files
Date: Wed, 4 May 2016 06:41:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605040637480.12063@localhost.localdomain> (raw)
In-Reply-To: <CADkTA4Ocu2L9GoBM4YadkGZJq+2Pd8UFA2acSeX4MSibEo-ZtA@mail.gmail.com>
one more question about fragments which i'm fairly sure i know the
answer to, but will be embarrassed about if i'm wrong.
if i want to set a kernel option in a fragment, i'm fairly certain i
need to *explicitly* set all options it depends on, correct?
otherwise, that option is left unselected.
is there any warning in a log file that mentions that happening?
rday
p.s. oh, and i think someone mentioned this earlier ... what happens
if i explicitly set one option, then explicitly "not set" another
option that is "select"ed by that first option? who wins?
ok, back to work ...
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-05-04 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 17:04 clarifying details about "is not set" lines in kernel config fragment files Robert P. J. Day
2016-05-03 18:10 ` Bruce Ashfield
2016-05-03 18:27 ` Robert P. J. Day
2016-05-03 18:45 ` Tom Rini
2016-05-03 20:05 ` Robert P. J. Day
2016-05-04 10:18 ` Robert P. J. Day
2016-05-03 18:48 ` Bruce Ashfield
2016-05-04 10:41 ` Robert P. J. Day [this message]
2016-05-04 12:13 ` Bruce Ashfield
2016-05-03 18:48 ` Denys Dmytriyenko
2016-05-03 20:06 ` 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.20.1605040637480.12063@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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