From: Martin Walch <walch.martin@web.de>
To: David Rientjes <rientjes@google.com>
Cc: linux-kbuild@vger.kernel.org, "Michal Marek" <mmarek@suse.cz>,
"Jiri Kosina" <trivial@kernel.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
"Arve Hjønnevåg" <arve@android.com>,
"Benjamin Poirier" <bpoirier@suse.de>,
"Dirk Gouders" <dirk@gouders.net>,
"Wang YanQing" <udknight@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jean Delvare" <jdelvare@suse.de>,
"Kees Cook" <keescook@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] kconfig: add short explanation to SYMBOL_WRITE
Date: Thu, 03 Oct 2013 02:26:49 +0200 [thread overview]
Message-ID: <49327842.0x8EUPeB87@tacticalops> (raw)
In-Reply-To: <alpine.DEB.2.02.1310021641280.9096@chino.kir.corp.google.com>
On Wednesday 02 October 2013 16:42:27 David Rientjes wrote:
> The purpose of SYMBOL_WRITE is in sym_calc_value() where it is set if the
> config symbol is visible and settable by the user, which is why I
> suggested it be specified as being writable by the user.
Then this looks strange to me: a config symbol of type boolean or tristate
that is not visible, but has a default value != n will have SYMBOL_WRITE set
in sym_calc_value:
> case S_BOOLEAN:
> case S_TRISTATE:
> if (sym_is_choice_value(sym) && sym->visible == yes) {
> ...
> } else {
> ...
> if (!sym_is_choice(sym)) {
> prop = sym_get_default_prop(sym);
> if (prop) {
> sym->flags |= SYMBOL_WRITE;
> newval.tri = EXPR_AND(expr_calc_value(prop->expr),
> prop->visible.tri);
> }
> }
> ...
> }
--
prev parent reply other threads:[~2013-10-03 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 5:24 [PATCH 1/4] kconfig: add short explanation to SYMBOL_WRITE Martin Walch
2013-10-02 5:24 ` Martin Walch
2013-10-02 5:37 ` David Rientjes
2013-10-02 23:39 ` Martin Walch
2013-10-02 23:42 ` David Rientjes
2013-10-03 0:26 ` Martin Walch [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=49327842.0x8EUPeB87@tacticalops \
--to=walch.martin@web.de \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=bpoirier@suse.de \
--cc=dirk@gouders.net \
--cc=jdelvare@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rientjes@google.com \
--cc=trivial@kernel.org \
--cc=udknight@gmail.com \
--cc=yann.morin.1998@free.fr \
/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.