From: Ralf Baechle <ralf@uni-koblenz.de>
To: Philip Blundell <philb@gnu.org>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Abramo Bagnara <abramo@alsa-project.org>,
linux@arm.linux.org.uk, davem@caip.rutgers.edu,
anton@linuxcare.com.au, linux-kernel@vger.kernel.org
Subject: Re: Inconsistent "#ifdef __KERNEL__" on different architectures
Date: Wed, 30 May 2001 00:30:01 +0200 [thread overview]
Message-ID: <20010530003001.A2864@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.NEB.4.33.0105272301280.8551-100000@mimas.fachschaften.tu-muenchen.de> <bunk@fs.tum.de> <E1548jY-0004D2-00@kings-cross.london.uk.eu.org>
In-Reply-To: <E1548jY-0004D2-00@kings-cross.london.uk.eu.org>; from philb@gnu.org on Sun, May 27, 2001 at 11:10:00PM +0100
On Sun, May 27, 2001 at 11:10:00PM +0100, Philip Blundell wrote:
> >--- include/asm-arm/atomic.h.old Sun May 27 22:30:58 2001
> >+++ include/asm-arm/atomic.h Sun May 27 22:58:20 2001
> >@@ -12,6 +12,7 @@
> > * 13-04-1997 RMK Made functions atomic!
> > * 07-12-1997 RMK Upgraded for v2.1.
> > * 26-08-1998 PJB Added #ifdef __KERNEL__
> >+ * 27-05-2001 APB Removed #ifdef __KERNEL__
> > */
> > #ifndef __ASM_ARM_ATOMIC_H
> > #define __ASM_ARM_ATOMIC_H
> >@@ -30,7 +31,6 @@
>
> This is no good. The ARM kernel just doesn't provide any atomic primitives
> that will work in user space. If you want atomicity you have to use
> libpthread.
Similar on some MIPS processors where the kernel has to implement atomic
operations because there is no practical possibility to implement them
in userspace.
Ralf
next prev parent reply other threads:[~2001-05-29 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 17:25 Inconsistent "#ifdef __KERNEL__" on different architectures Adrian Bunk
2001-05-27 17:29 ` Alan Cox
2001-05-27 19:16 ` Abramo Bagnara
2001-05-27 21:07 ` Adrian Bunk
2001-05-27 21:42 ` Russell King - ARM Linux
2001-05-27 22:10 ` Philip Blundell
2001-05-29 22:30 ` Ralf Baechle [this message]
2001-06-02 20:29 ` Adrian Bunk
2001-06-05 4:09 ` Paul Mackerras
2001-06-05 9:33 ` Adrian Bunk
2001-06-05 12:15 ` Paul Mackerras
2001-06-06 6:51 ` Albert D. Cahalan
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=20010530003001.A2864@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=abramo@alsa-project.org \
--cc=anton@linuxcare.com.au \
--cc=bunk@fs.tum.de \
--cc=davem@caip.rutgers.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.