From: Nick Piggin <npiggin@suse.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch][rfc] rwsem: generic rwsem
Date: Mon, 4 Dec 2006 11:25:37 +0100 [thread overview]
Message-ID: <20061204102537.GA30390@wotan.suse.de> (raw)
In-Reply-To: <20061204100607.GA20529@wotan.suse.de>
On Mon, Dec 04, 2006 at 11:06:07AM +0100, Nick Piggin wrote:
> (resending with correct ML addresses, sorry)
>
> Hi,
>
> This patch needs review and testing from the architecture guys, but
> I would like to consider it because of the obvious maintenance benefits.
Hah, very important detail: patch is on top of Mathieu Desnoyers' recent
"[PATCH 1/2] atomic.h atomic64_t standardization", which gives us
atomic_long_cmpxchg on all architectures.
Nick
next prev parent reply other threads:[~2006-12-04 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 10:06 [patch][rfc] rwsem: generic rwsem Nick Piggin
2006-12-04 10:25 ` Nick Piggin [this message]
2006-12-04 12:55 ` David Howells
2006-12-04 14:46 ` Nick Piggin
2006-12-05 20:36 ` David Howells
2006-12-08 2:22 ` Nick Piggin
2006-12-08 13:58 ` David Howells
2006-12-11 4:03 ` Nick Piggin
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=20061204102537.GA30390@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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