From: Stephen Clark <sclark46@earthlink.net>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Developers <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH v2] Documentation: rw_lock lessons learned
Date: Thu, 12 Nov 2009 14:13:03 -0500 [thread overview]
Message-ID: <4AFC5E3F.7070609@earthlink.net> (raw)
In-Reply-To: <4AFBEC44.9030409@gmail.com>
William Allen Simpson wrote:
> In recent weeks, two different network projects erroneously
> strayed down the rw_lock path. Update the Documentation
> based upon comments by Eric Dumazet and Paul E. McKenney in
> those threads.
>
> Merged with editorial changes by Stephen Hemminger.
>
> Signed-off-by: William.Allen.Simpson@gmail.com
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> Documentation/spinlocks.txt | 186
> ++++++++++++++++++++-----------------------
> 1 files changed, 86 insertions(+), 100 deletions(-)
>
How up to date is this doc?
http://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/index.html
Should it be in the Documentation directory?
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2009-11-12 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 19:55 [PATCH resent] Documentation: rw_lock lessons learned William Allen Simpson
2009-11-10 21:22 ` Paul E. McKenney
2009-11-11 2:06 ` Stephen Hemminger
2009-11-11 17:08 ` William Allen Simpson
2009-11-11 17:37 ` Stephen Hemminger
2009-11-12 11:06 ` [PATCH v2] " William Allen Simpson
2009-11-12 15:40 ` Linus Torvalds
2009-11-12 17:04 ` Stephen Hemminger
2009-11-12 19:13 ` Stephen Clark [this message]
2009-11-12 23:00 ` Stephen Hemminger
2009-11-13 8:59 ` Stefan Richter
2009-11-13 16:15 ` William Allen Simpson
2009-12-11 17:01 ` [PATCH v2] " William Allen Simpson
2009-12-11 21:07 ` Jarek Poplawski
2009-12-12 10:36 ` William Allen Simpson
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=4AFC5E3F.7070609@earthlink.net \
--to=sclark46@earthlink.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=shemminger@vyatta.com \
--cc=torvalds@linux-foundation.org \
--cc=william.allen.simpson@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).