lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 11 Nov 2009 09:37:24 -0800
From:	Stephen Hemminger <>
To:	William Allen Simpson <>
Cc:	"Paul E. McKenney" <>,
	Linus Torvalds <>,
	Linux Kernel Developers <>,
	Linux Kernel Network Developers <>,
	Eric Dumazet <>
Subject: Re: [PATCH resent] Documentation: rw_lock lessons learned

On Wed, 11 Nov 2009 12:08:08 -0500
William Allen Simpson <> wrote:

> 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?

Sure, I am more concerned about document structure being readable than
preserving my sloppy prose.

> Or this is a second patch in a proposed series?

No. But taking more input from others (maybe Randy will help he is a good
editor) would get this back in shape.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists