public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, will.deacon@arm.com,
	peterz@infradead.org, benh@kernel.crashing.org,
	linux-arch@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL rcu/next] Additional RCU commit for 4.3
Date: Tue, 25 Aug 2015 09:46:31 +0200	[thread overview]
Message-ID: <20150825074631.GA25158@gmail.com> (raw)
In-Reply-To: <20150825000311.GA32412@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> This additional series contains a single change:
> 
> 1.	Privatize smp_mb__after_unlock_lock().  This commit moves the
> 	definition of smp_mb__after_unlock_lock() to kernel/rcu/tree.h,
> 	in recognition of the fact that RCU is the only thing using
> 	this, that nothing else is likely to use it, and that it is
> 	likely to go away completely.
> 
> This change has been subjected to 0day Test Robot and -next testing,
> and is available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
> 
> for you to fetch changes up to 12d560f4ea87030667438a169912380be00cea4b:
> 
>   rcu,locking: Privatize smp_mb__after_unlock_lock() (2015-08-04 08:49:21 -0700)
> 
> ----------------------------------------------------------------
> Paul E. McKenney (1):
>       rcu,locking: Privatize smp_mb__after_unlock_lock()
> 
>  Documentation/memory-barriers.txt   | 71 +++----------------------------------
>  arch/powerpc/include/asm/spinlock.h |  2 --
>  include/linux/spinlock.h            | 10 ------
>  kernel/rcu/tree.h                   | 12 +++++++
>  4 files changed, 16 insertions(+), 79 deletions(-)

Pulled, thanks a lot Paul!

	Ingo

           reply	other threads:[~2015-08-25  7:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20150825000311.GA32412@linux.vnet.ibm.com>]

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=20150825074631.GA25158@gmail.com \
    --to=mingo@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.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