[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1477690012.2167.21.camel@tiscali.nl>
Date: Fri, 28 Oct 2016 23:26:52 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: John Stultz <john.stultz@...aro.org>,
Richard Cochran <richardcochran@...il.com>,
Michal Marek <mmarek@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Triplett <josh@...htriplett.org>,
Edward Cree <ecree@...arflare.com>, netdev@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] kconfig: introduce the "imply" keyword
On Thu, 2016-10-27 at 23:10 -0400, Nicolas Pitre wrote:
> On Fri, 28 Oct 2016, Paul Bolle wrote:
> > You probably got "["if" <expr>]" for free by copying what's there for
> > select. But this series doesn't use it, so perhaps it would be better
> > to not document it yet. But that is rather sneaky. Dunno.
>
> If it is not documented then the chance that someone uses it are slim.
> And since it comes "for free" I don't see the point of making the tool
> less flexible. And not having this flexibility could make some
> transitions from "select" to "imply" needlessly difficult.
My point is moot. I somehow missed that this series adds
imply PTP_1588_CLOCK if TILEGX
So you are quite right in documenting this.
Paul Bolle
Powered by blists - more mailing lists