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);
> }
> }
> ...
> }
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
