From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
paul.mckenney@linaro.org, mmarek@suse.cz,
linux-kbuild@vger.kernel.org
Subject: Re: rcu: Provide compile-time control for no-CBs CPUs
Date: Tue, 30 Apr 2013 15:19:15 -0700 [thread overview]
Message-ID: <20130430221915.GM3780@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130430220647.GA16524@redhat.com>
On Tue, Apr 30, 2013 at 06:06:47PM -0400, Dave Jones wrote:
> On Tue, Apr 30, 2013 at 02:48:26PM -0700, Paul E. McKenney wrote:
>
> > <snip excellent explanation>
> >
> > Should I add this to the Kconfig help text? My guess is "not all of it",
> > but figured I should ask.
>
> The commit msg would have been a great place for much of it, especially
> the part explaining your desire to have users kick the tires etc.
Good point, will keep that in mind for next time.
> > See below for my current best guess.
>
> Much better. Be sure to pass on the 'terrible kconfig' award to the
> next lucky recipient when their time comes :)
Interesting. Who passed it to you, and what was the occasion? ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-04-30 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130430152126.0C564660906@gitolite.kernel.org>
2013-04-30 18:46 ` rcu: Provide compile-time control for no-CBs CPUs Dave Jones
2013-04-30 19:25 ` Paul E. McKenney
2013-04-30 20:24 ` Dave Jones
2013-04-30 21:48 ` Paul E. McKenney
2013-04-30 22:06 ` Dave Jones
2013-04-30 22:19 ` Paul E. McKenney [this message]
2013-04-30 21:38 ` Yann E. MORIN
2013-04-30 21:49 ` Paul E. McKenney
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=20130430221915.GM3780@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=paul.mckenney@linaro.org \
/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.