public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Michal Hocko <mhocko@suse.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Cleanup PATCH] rcu: Do not use rcu_read_lock_held when calling rcu_dereference_check
Date: Fri, 8 Jul 2011 13:46:32 -0700	[thread overview]
Message-ID: <20110708204632.GZ6014@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1107082222150.11049@pobox.suse.cz>

On Fri, Jul 08, 2011 at 10:22:45PM +0200, Jiri Kosina wrote:
> On Fri, 8 Jul 2011, Paul E. McKenney wrote:
> 
> > > Hmm, thinking about it some more. Wouldn't it make more sense to push
> > > this through trivial tree (CCing Jikos)? Having 5 or so patches with the
> > > exactly same changelog sounds overkill to me.
> > > 
> > > What do you think? Could you give me your Acked-by if you are OK with
> > > it, please?
> > 
> > Whatever works.  ;-)
> > 
> > However, I did queue the Documentation/RCU/lockdep.txt patch already.
> 
> That's no problem for git. But anyway, I have dropped that part.
> 
> > For the others,
> > 
> > Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> 
> Thanks. Applied.

Thank you, Jiri!

							Thanx, Paul

  reply	other threads:[~2011-07-08 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 13:57 [Cleanup PATCH] rcu: Do not use rcu_read_lock_held when calling rcu_dereference_check Michal Hocko
2011-07-08 15:48 ` Paul E. McKenney
2011-07-08 15:57   ` Michal Hocko
2011-07-08 16:30     ` Michal Hocko
2011-07-08 18:51       ` Paul E. McKenney
2011-07-08 20:22         ` Jiri Kosina
2011-07-08 20:46           ` Paul E. McKenney [this message]
2011-07-09 10:58             ` Michal Hocko

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=20110708204632.GZ6014@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    /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