[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNATbquS2RDGDK0xYv9bG8UsqFh9HXiyUR-BF995qQ3OjMQ@mail.gmail.com>
Date: Fri, 19 Jan 2018 01:47:03 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Ulf Magnusson <ulfalizer@...il.com>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kconfig: Clarify choice dependency propagation
2018-01-14 23:12 GMT+09:00 Ulf Magnusson <ulfalizer@...il.com>:
> It's easy to miss that choices are special-cased to pass on their mode
> as the parent dependency.
>
> No functional changes. Only comments added.
>
> Signed-off-by: Ulf Magnusson <ulfalizer@...il.com>
> ---
> scripts/kconfig/menu.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
> index 92d3f06cd8a2..53964d911708 100644
> --- a/scripts/kconfig/menu.c
> +++ b/scripts/kconfig/menu.c
> @@ -323,6 +323,13 @@ void menu_finalize(struct menu *parent)
> if (menu->sym && menu->sym->type == S_UNKNOWN)
> menu_set_type(sym->type);
> }
> +
> + /*
> + * Use the choice itself as the parent dependency of
> + * the contained items. This turns the mode of the
> + * choice into an upper bound on the visibility of the
> + * choice symbols.
> + */
Does the last "choice symbols" mean "choice values"?
The "choice" itself is a symbol with NULL name,
so I'd like to clarify it.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists