From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, sasha.levin@oracle.com
Subject: [GIT PULL rcu/next] One more RCU commit for 3.20
Date: Mon, 16 Feb 2015 20:47:51 -0800 [thread overview]
Message-ID: <20150217044751.GA9654@linux.vnet.ibm.com> (raw)
Hello, Ingo,
One more change that I should have included in my last pull, namely a
change that prevents a splat seen by Sasha Levin. This commit passes
testing (including of course Sasha's), has been exposed to both -next
and 0day testing, and is quite small.
This change is available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
for you to fetch changes up to c0135d07b013fa8f7ba9ec91b4369c372e6a28cb:
rcu: Clear need_qs flag to prevent splat (2015-02-11 15:46:43 -0800)
----------------------------------------------------------------
Paul E. McKenney (1):
rcu: Clear need_qs flag to prevent splat
kernel/rcu/tree_plugin.h | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2015-02-17 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 4:47 Paul E. McKenney [this message]
2015-02-18 17:00 ` [GIT PULL rcu/next] One more RCU commit for 3.20 Ingo Molnar
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=20150217044751.GA9654@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox