From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Roland Dreier <rdreier@cisco.com>,
Andy Fleming <afleming@freescale.com>,
Ben Collins <ben.collins@ubuntu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] Export current_is_keventd() for libphy
Date: Wed, 06 Dec 2006 18:43:22 +0000 [thread overview]
Message-ID: <16935.1165430602@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612061017220.3542@woody.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> (a) "volatile" on kernel data is basically always a bug, and you should
> use locking.
But what about when you're building a lock? Actually, I suspect correct usage
of asm constraints and memory barriers trumps volatile anyway even there.
David
next prev parent reply other threads:[~2006-12-06 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0612060822260.3542@woody.osdl.org>
[not found] ` <1165125055.5320.14.camel@gullible>
[not found] ` <20061203011625.60268114.akpm@osdl.org>
[not found] ` <Pine.LNX.4.64N.0612051642001.7108@blysk.ds.pg.gda.pl>
[not found] ` <20061205123958.497a7bd6.akpm@osdl.org>
[not found] ` <6FD5FD7A-4CC2-481A-BC87-B869F045B347@freescale.com>
[not found] ` <20061205132643.d16db23b.akpm@osdl.org>
[not found] ` <adaac22c9cu.fsf@cisco.com>
[not found] ` <20061205135753.9c3844f8.akpm@osdl.org>
[not found] ` <Pine.LNX.4.64N.0612061506460.29000@blysk.ds.pg.gda.pl>
[not found] ` <20061206075729.b2b6aa52.akpm@osdl.org>
[not found] ` <21690.1165426993@redhat.com>
[not found] ` <Pine.LNX.4.64.0612060951150.3542@woody.osdl.org>
[not found] ` <Pine.LNX.4.64.0612060955380.3542@woody.osdl.org>
2006-12-06 18:33 ` [PATCH] Export current_is_keventd() for libphy Linus Torvalds
2006-12-06 18:37 ` Linus Torvalds
2006-12-06 18:43 ` David Howells [this message]
2006-12-06 19:02 ` Linus Torvalds
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=16935.1165430602@redhat.com \
--to=dhowells@redhat.com \
--cc=afleming@freescale.com \
--cc=akpm@osdl.org \
--cc=ben.collins@ubuntu.com \
--cc=jeff@garzik.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=rdreier@cisco.com \
--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