From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: [GIT PULL rcu/urgent] Make SRCU be built by default
Date: Tue, 25 Apr 2017 12:18:37 -0700 [thread overview]
Message-ID: <20170425191837.GA9101@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This commit causes SRCU to be built by default. This handles the
surprisingly common case where include/linux/srcu.h is included
into files being built with CONFIG_SRCU=n. The fact that there is
now a Tiny SRCU means that this should be OK from a Linux-kernel
tinification perspective. The following changes since commit
677df9d4615a ("srcu: Fix Kconfig botch when SRCU not selected"):
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
for you to fetch changes up to d160a727c40e7175aa642137910a3fda46262fc8:
srcu: Make SRCU be built by default (2017-04-24 08:36:02 -0700)
----------------------------------------------------------------
Paul E. McKenney (1):
srcu: Make SRCU be built by default
init/Kconfig | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2017-04-25 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 19:18 Paul E. McKenney [this message]
2017-04-26 5:41 ` [GIT PULL rcu/urgent] Make SRCU be built by default 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=20170425191837.GA9101@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox