lists.openwall.net | 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
| ||
|
Date: Wed, 11 Nov 2009 12:08:08 -0500 From: William Allen Simpson <william.allen.simpson@...il.com> To: Stephen Hemminger <shemminger@...tta.com> CC: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel Developers <linux-kernel@...r.kernel.org>, Linux Kernel Network Developers <netdev@...r.kernel.org>, Eric Dumazet <eric.dumazet@...il.com> Subject: Re: [PATCH resent] Documentation: rw_lock lessons learned 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists