All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Add Documentation/RCU/00-Index
Date: Thu, 11 Oct 2007 16:52:38 -0700	[thread overview]
Message-ID: <20071011235238.GA8401@linux.vnet.ibm.com> (raw)
In-Reply-To: <200710111823.27396.rob@landley.net>

On Thu, Oct 11, 2007 at 06:23:27PM -0500, Rob Landley wrote:
> From: Rob Landley <rob@landley.net>
> 
> Add Documentation/RCU/00-INDEX

Good addition!!!

Acked-by: Paul E. McKenney <paulmck@us.ibm.com>

> Signed-off-by: Rob Landley <rob@landley.net>
> ---
> 
>  Documentation/RCU/00-INDEX |   22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> --- /dev/null	2007-04-23 10:59:00.000000000 -0500
> +++ hg/Documentation/RCU/00-INDEX	2007-10-11 18:17:26.000000000 -0500
> @@ -0,0 +1,22 @@
> +00-INDEX
> +	- This file
> +arrayRCU.txt
> +	- Using RCU to Protect Read-Mostly Arrays
> +checklist.txt
> +	- Review Checklist for RCU Patches
> +listRCU.txt
> +	- Using RCU to Protect Read-Mostly Linked Lists
> +NMI-RCU.txt
> +	- Using RCU to Protect Dynamic NMI Handlers
> +rcuref.txt
> +	- Reference-count design for elements of lists/arrays protected by RCU
> +rcu.txt
> +	- RCU Concepts
> +RTFP.txt
> +	- List of RCU papers (bibliography) going back to 1980.
> +torture.txt
> +	- RCU Torture Test Operation (CONFIG_RCU_TORTURE_TEST)
> +UP.txt
> +	- RCU on Uniprocessor Systems
> +whatisRCU.txt
> +	- What is RCU?
> 
> -- 
> "One of my most productive days was throwing away 1000 lines of code."
>   - Ken Thompson.

      reply	other threads:[~2007-10-11 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 23:23 [PATCH] Add Documentation/RCU/00-Index Rob Landley
2007-10-11 23:52 ` Paul E. McKenney [this message]

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=20071011235238.GA8401@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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.