All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: John Stultz <john.stultz@linaro.org>,
	Richard Cochran <richardcochran@gmail.com>,
	Michal Marek <mmarek@suse.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Josh Triplett <josh@joshtriplett.org>,
	Edward Cree <ecree@solarflare.com>,
	netdev@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] kconfig: introduce the "imply" keyword
Date: Sat, 29 Oct 2016 00:09:05 +0200	[thread overview]
Message-ID: <1477692545.2167.42.camel@tiscali.nl> (raw)
In-Reply-To: <alpine.LFD.2.20.1610272156050.14694@knanqh.ubzr>

On Thu, 2016-10-27 at 23:10 -0400, Nicolas Pitre wrote:
> On Fri, 28 Oct 2016, Paul Bolle wrote:
> > And in your example BAR is bool, right? Does the above get more
> > complicated if BAR would be tristate?
> 
> If BAR=m then implying BAZ from FOO=y will force BAZ to y or n, 
> bypassing the restriction provided by BAR like "select" does.  This is 
> somewhat questionable for "select" to do that, and the code emits a 
> warning when "select" bypasses a direct dependency set to n, but not 
> when set to m. For now "imply" simply tries to be consistent with 
> the "select" behavior.

Side note: yes, one can select a symbol that's missing one or more
dependencies. But since Kconfig has two separate methods to describe
relations (ie, selecting and depending) there's logically the
possibility of conflict. So we need a rule to resolve that conflict.
That rule is: "select" beats "depends on". I don't think that this rule
is less plausible than the opposite rule.


Paul Bolle

  parent reply	other threads:[~2016-10-28 22:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  2:28 Nicolas Pitre
2016-10-26  2:28 ` (unknown), Nicolas Pitre
2016-10-26  2:28 ` [PATCH v2 1/5] kconfig: introduce the "imply" keyword Nicolas Pitre
2016-10-26 23:28   ` Paul Bolle
2016-10-26 23:44     ` Nicolas Pitre
2016-10-28  0:17   ` Paul Bolle
2016-10-28  3:10     ` Nicolas Pitre
2016-10-28 21:26       ` Paul Bolle
2016-10-28 21:31       ` Paul Bolle
2016-10-28 22:03         ` Nicolas Pitre
2016-10-28 22:09       ` Paul Bolle [this message]
2016-10-26  2:28 ` [PATCH v2 2/5] kconfig: introduce the "suggest" keyword Nicolas Pitre
2016-10-27  0:10   ` Paul Bolle
2016-10-27  2:39     ` Nicolas Pitre
2016-10-26  2:28 ` [PATCH v2 3/5] kconfig: regenerate *.c_shipped files after previous changes Nicolas Pitre
2016-10-26  2:28 ` [PATCH v2 4/5] ptp_clock: allow for it to be optional Nicolas Pitre
2016-10-26  2:28 ` [PATCH v2 5/5] posix-timers: make it configurable Nicolas Pitre
2016-10-26  8:51   ` Richard Cochran
2016-10-26 13:56     ` Nicolas Pitre
2016-10-26 20:18       ` Richard Cochran
2016-10-26 22:49         ` Nicolas Pitre
2016-10-26 23:14 ` [PATCH v2 0/5] make POSIX timers optional with some Kconfig help Paul Bolle
2016-10-26 23:41   ` Nicolas Pitre
2016-10-26 23:52     ` Paul Bolle
2016-10-28 22:50 ` Paul Bolle
2016-10-29  2:00   ` Nicolas Pitre

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=1477692545.2167.42.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=ecree@solarflare.com \
    --cc=john.stultz@linaro.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    /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.