From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org,
Dipankar Sarma <dipankar@in.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 1/5] rcu: uninline __rcu_pending()
Date: Sun, 8 Jan 2006 21:27:03 -0800 [thread overview]
Message-ID: <20060109052703.GA12917@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601082017220.3169@g5.osdl.org>
On Sun, Jan 08, 2006 at 08:17:51PM -0800, Linus Torvalds wrote:
>
> Paul,
> RCU patches always make me worry, so can you please Ack or Nack this
> series?
Me too, especially mine!
I will look this over carefully and either Ack or Nack with diagnostics.
Thanx, Paul
next prev parent reply other threads:[~2006-01-09 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 19:19 [PATCH 1/5] rcu: uninline __rcu_pending() Oleg Nesterov
2006-01-09 4:17 ` Linus Torvalds
2006-01-09 5:27 ` Paul E. McKenney [this message]
2006-01-09 17:20 ` Paul E. McKenney
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=20060109052703.GA12917@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=oleg@tv-sign.ru \
--cc=torvalds@osdl.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