From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: John Stultz <john.stultz@linaro.org>,
Richard Cochran <richardcochran@gmail.com>,
Yann E MORIN <yann.morin.1998@free.fr>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Triplett <josh@joshtriplett.org>,
netdev@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] kconfig: introduce the "imply" keyword
Date: Thu, 20 Oct 2016 15:53:28 +0900 [thread overview]
Message-ID: <CAK7LNAQ3UCFXOsCU6t_RJfe4Suxz3BmJGaBw7fMTy=z8JoJ2Bw@mail.gmail.com> (raw)
In-Reply-To: <1476920573-14384-2-git-send-email-nicolas.pitre@linaro.org>
2016-10-20 8:42 GMT+09:00 Nicolas Pitre <nicolas.pitre@linaro.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
next prev parent reply other threads:[~2016-10-20 6:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 23:42 [PATCH 0/4] make POSIX timers optional with some Kconfig help Nicolas Pitre
2016-10-19 23:42 ` [PATCH 1/4] kconfig: introduce the "imply" keyword Nicolas Pitre
2016-10-20 6:53 ` Masahiro Yamada [this message]
2016-10-20 14:52 ` Edward Cree
2016-10-20 15:38 ` Josh Triplett
2016-10-20 17:04 ` Nicolas Pitre
2016-10-20 17:41 ` Edward Cree
2016-10-20 18:29 ` Nicolas Pitre
2016-10-20 19:09 ` Edward Cree
2016-10-20 20:10 ` Nicolas Pitre
2016-10-21 3:24 ` Nicolas Pitre
2016-10-19 23:42 ` [PATCH 2/4] kconfig: re-generate *.c_shipped files after previous change Nicolas Pitre
2016-10-19 23:42 ` [PATCH 3/4] ptp_clock: allow for it to be optional Nicolas Pitre
2016-10-20 9:50 ` Thomas Gleixner
2016-10-20 17:47 ` Nicolas Pitre
2016-10-20 17:58 ` Thomas Gleixner
2016-10-20 14:06 ` Richard Cochran
2016-10-20 15:38 ` Josh Triplett
2016-10-20 16:44 ` Nicolas Pitre
2016-10-19 23:42 ` [PATCH 4/4] posix-timers: make it configurable Nicolas Pitre
2016-10-20 14:02 ` Richard Cochran
2016-10-20 16:41 ` Nicolas Pitre
2016-10-20 9:46 ` [PATCH 0/4] make POSIX timers optional with some Kconfig help Thomas Gleixner
2016-10-20 18:35 ` Nicolas Pitre
2016-10-20 18:51 ` Josh Triplett
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='CAK7LNAQ3UCFXOsCU6t_RJfe4Suxz3BmJGaBw7fMTy=z8JoJ2Bw@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).