From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "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 resent] Documentation: rw_lock lessons learned
Date: Wed, 11 Nov 2009 12:08:08 -0500 [thread overview]
Message-ID: <4AFAEF78.4080807@gmail.com> (raw)
In-Reply-To: <20091110180646.2e5859a8@nehalam>
Stephen Hemminger wrote:
> I would rather see the text in Documentation/spinlocks give an explaination
> as to why reader/writer locks are normally not desirable.
>
> The whole document needs work to make it a developer document, rather than
> a historical mail thread.. A good document says what should be done today,
> and does not have old junk or ask the reader to overly new context
> on old information.
>
You wish me to merge our patches?
Or this is a second patch in a proposed series?
next prev parent reply other threads:[~2009-11-11 17:08 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 [this message]
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
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=4AFAEF78.4080807@gmail.com \
--to=william.allen.simpson@gmail.com \
--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 \
/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).