From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v3.15
Date: Tue, 1 Apr 2014 16:04:19 -0700 [thread overview]
Message-ID: <20140401230419.GA22622@linux.vnet.ibm.com> (raw)
In-Reply-To: <1396385946.23763.34.camel@x220>
On Tue, Apr 01, 2014 at 10:59:06PM +0200, Paul Bolle wrote:
> On Tue, 2014-04-01 at 13:52 -0700, Paul E. McKenney wrote:
> > I don't believe that this is particularly urgent, so unless someone
> > tells me otherwise, I will queue the fix for 3.16.
>
> Few people share my OCD for Kconfig symbols. So most people will not
> think this is urgent. On the other hand, why wait three to four months
> when this can be cleaned up in a few weeks?
Because I need to decide whether the right fix is to add the
LOCK_TORTURE_RUNNABLE or to remove the RCU_TORTURE_RUNNABLE. ;-)
My kneejerk reaction was the former, but I am leaning towards the latter.
Shrinks the code a bit, gets rid of a Kconfig parameter and only requires
changes in scripts for a few people using rcutorture...
Thanx, Paul
prev parent reply other threads:[~2014-04-01 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 8:17 [GIT PULL] RCU changes for v3.15 Ingo Molnar
2014-04-01 20:31 ` Paul Bolle
2014-04-01 20:52 ` Paul E. McKenney
2014-04-01 20:59 ` Paul Bolle
2014-04-01 23:04 ` Paul E. McKenney [this message]
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=20140401230419.GA22622@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.