From: Ingo Molnar <mingo@elte.hu>
To: Gautham R Shenoy <ego@in.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Paul E McKenney <paulmck@us.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>, Ted Tso <tytso@us.ibm.com>,
dvhltc@us.ibm.com, Oleg Nesterov <oleg@tv-sign.ru>,
Andrew Morton <akpm@linux-foundation.org>,
bunk@kernel.org, Josh Triplett <josh@freedesktop.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC PATCH 6/6] Preempt-RCU: Update RCU Documentation.
Date: Thu, 13 Dec 2007 21:42:53 +0100 [thread overview]
Message-ID: <20071213204253.GG25130@elte.hu> (raw)
In-Reply-To: <20071213171814.GG25981@in.ibm.com>
* Gautham R Shenoy <ego@in.ibm.com> wrote:
> Preempt-RCU: Update RCU Documentation.
>
> From: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> This patch updates the RCU documentation to reflect preemptible RCU as
> well as recent publications.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Gautham, this patch is missing your SoB line - could you please send it?
Ingo
next prev parent reply other threads:[~2007-12-13 20:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 17:03 [RFC PATCH 0/6] RCU: Preemptible-RCU Gautham R Shenoy
2007-12-13 17:14 ` [RFC PATCH 1/6] Preempt-RCU: Use softirq instead of tasklets for RCU Gautham R Shenoy
2007-12-13 17:15 ` [RFC PATCH 2/6] Preempt-RCU: Reorganize RCU code into rcuclassic.c and rcupdate.c Gautham R Shenoy
2007-12-14 14:51 ` Johannes Weiner
2007-12-14 16:12 ` Paul E. McKenney
2007-12-13 17:16 ` [RFC PATCH 3/6] Preempt-RCU: Fix rcu_barrier for preemptive environment Gautham R Shenoy
2007-12-13 17:16 ` [RFC PATCH 4/6] Preempt-RCU: Implementation Gautham R Shenoy
2007-12-13 17:16 ` Gautham R Shenoy
2008-02-29 4:34 ` Roman Zippel
2008-02-29 4:53 ` Paul E. McKenney
2008-02-29 12:38 ` Roman Zippel
2008-02-29 13:55 ` Steven Rostedt
2008-03-01 19:39 ` Paul E. McKenney
2008-03-01 21:07 ` Steven Rostedt
2008-03-02 3:09 ` Roman Zippel
2008-03-02 3:06 ` Roman Zippel
2008-03-03 18:55 ` Paul E. McKenney
2008-03-04 20:22 ` [PATCH] move PREEMPT_RCU config option back under PREEMPT Paul E. McKenney
2008-03-04 20:55 ` Steven Rostedt
2008-03-05 0:58 ` Paul E. McKenney
2008-03-05 2:06 ` Roman Zippel
2008-03-05 19:00 ` Paul E. McKenney
2008-03-04 20:49 ` [RFC PATCH 4/6] Preempt-RCU: Implementation Roman Zippel
2008-02-29 13:53 ` Steven Rostedt
2008-02-29 14:31 ` Roman Zippel
2007-12-13 17:17 ` [RFC PATCH 5/6] Preempt-RCU: CPU Hotplug handling Gautham R Shenoy
2007-12-13 17:18 ` [RFC PATCH 6/6] Preempt-RCU: Update RCU Documentation Gautham R Shenoy
2007-12-13 17:18 ` Gautham R Shenoy
2007-12-13 20:42 ` Ingo Molnar [this message]
2007-12-13 21:06 ` Gautham R Shenoy
2007-12-13 17:36 ` [RFC PATCH 0/6] RCU: Preemptible-RCU Steven Rostedt
2007-12-13 20:42 ` Ingo Molnar
2007-12-13 20:56 ` Steven Rostedt
2007-12-13 21:09 ` Gautham R Shenoy
2007-12-13 20:38 ` Ingo Molnar
2007-12-13 23:41 ` 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=20071213204253.GG25130@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=ego@in.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=paulmck@us.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tytso@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.