[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAQ3UCFXOsCU6t_RJfe4Suxz3BmJGaBw7fMTy=z8JoJ2Bw@mail.gmail.com>
Date: Thu, 20 Oct 2016 15:53:28 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: John Stultz <john.stultz@...aro.org>,
Richard Cochran <richardcochran@...il.com>,
Yann E MORIN <yann.morin.1998@...e.fr>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Triplett <josh@...htriplett.org>, netdev@...r.kernel.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] kconfig: introduce the "imply" keyword
2016-10-20 8:42 GMT+09:00 Nicolas Pitre <nicolas.pitre@...aro.org>:
> diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
> index 069fcb3eef..c96127f648 100644
> --- a/Documentation/kbuild/kconfig-language.txt
> +++ b/Documentation/kbuild/kconfig-language.txt
> @@ -113,6 +113,33 @@ applicable everywhere (see syntax).
> That will limit the usefulness but on the other hand avoid
> the illegal configurations all over.
>
> +- weak reverse dependencies: "imply" <symbol> ["if" <expr>]
> + This is similar to "select" as it enforces a lower limit on another
> + symbol except that the "implied" config symbol's value may still be
> + set to n from a direct dependency or with a visible prompt.
> + Given the following example:
> +
> + config FOO
> + tristate
> + imply BAZ
> +
> + config BAZ
> + tristate
> + depends on BAr
s/BAr/BAR/ ?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists