From: Russell King <rmk@arm.linux.org.uk>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: atomic_t (24 bits???)
Date: Tue, 25 Feb 2003 21:57:15 +0000 [thread overview]
Message-ID: <20030225215715.H21014@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030225191711.GA25331@nevyn.them.org>; from dan@debian.org on Tue, Feb 25, 2003 at 02:17:11PM -0500
On Tue, Feb 25, 2003 at 02:17:11PM -0500, Daniel Jacobowitz wrote:
> There are other platforms where you can't reliably use the whole word.
> Some ARM atomic_t implementations are like this, although I don't know
> if the one in the kernel is.
The ARM atomic_t isn't 24-bit - it's a full paid up member of the
32-bit club. 8)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-02-25 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 19:11 atomic_t (24 bits???) Richard B. Johnson
2003-02-25 19:14 ` Roman Zippel
2003-02-25 19:31 ` Richard B. Johnson
2003-02-25 19:17 ` Daniel Jacobowitz
2003-02-25 19:31 ` Richard B. Johnson
2003-02-25 21:57 ` Russell King [this message]
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=20030225215715.H21014@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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