From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Doc/RCU: fix pseudocode in rcuref.txt
Date: Wed, 10 Sep 2008 08:40:34 -0700 [thread overview]
Message-ID: <20080910154034.GF6742@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080910063745.GC14700@elte.hu>
On Wed, Sep 10, 2008 at 08:37:45AM +0200, Ingo Molnar wrote:
>
> * Lai Jiangshan <laijs@cn.fujitsu.com> wrote:
>
> > atomic_inc_not_zero(v) return 0 if *v = 0.
> > use spin_lock instead of write_lock for update lock.
> >
> > Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>
> i've applied it to tip/core/rcu (unless Paul has objections) - thanks!
No objections here!!!
Thanx, Paul
next prev parent reply other threads:[~2008-09-10 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 3:01 [PATCH] Doc/RCU: fix pseudocode in rcuref.txt Lai Jiangshan
2008-09-10 6:37 ` Ingo Molnar
2008-09-10 15:40 ` Paul E. McKenney [this message]
2008-09-10 15:40 ` 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=20080910154034.GF6742@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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