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: Fri, 28 Oct 2016 23:26:52 +0200 [thread overview]
Message-ID: <1477690012.2167.21.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:
> > 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
next prev parent reply other threads:[~2016-10-28 21:27 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 [this message]
2016-10-28 21:31 ` Paul Bolle
2016-10-28 22:03 ` Nicolas Pitre
2016-10-28 22:09 ` Paul Bolle
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=1477690012.2167.21.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.