From: Peter Fritzsche <peter.fritzsche@gmx.de>
To: David Howells <dhowells@redhat.com>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
Ingo Molnar <mingo@elte.hu>,
Remis Lima Baima <remis.developer@googlemail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-am33-list@redhat.com, linux-kernel@vger.kernel.org,
Keith M Wesolowski <wesolows@foobazco.org>
Cc: Peter Fritzsche <peter.fritzsche@gmx.de>
Subject: [PATCH 1/2] mn10300: Don't warn that atomic_t is only 24 bit
Date: Wed, 28 Apr 2010 12:50:37 +0200 [thread overview]
Message-ID: <1272451837-17961-1-git-send-email-peter.fritzsche@gmx.de> (raw)
32-bit Sparc used to only allow usage of 24-bit of it's atomic_t type.
This was corrected with linux 2.6.3 when Keith M Wesolowski changed the
implementation to use the parisc approach of having an array of
spinlocks to protect the atomic_t.
These warnings were also removed from the sparc implementation when the
new implementation was merged in BKrev:402e4949VThdc6D3iaosSFUgabMfvw,
but the warning still remained in some other places without any
24-bit-only atomic_t implementation inside the kernel.
We should remove these warnings to allow users to rely on the full
32-bit range of atomic_t.
Signed-off-by: Peter Fritzsche <peter.fritzsche@gmx.de>
---
This should correct the problem mentioned in http://lkml.org/lkml/2010/4/26/33
arch/mn10300/include/asm/atomic.h | 8 ++------
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/mn10300/include/asm/atomic.h b/arch/mn10300/include/asm/atomic.h
index 5bf5be9..5b58ff8 100644
--- a/arch/mn10300/include/asm/atomic.h
+++ b/arch/mn10300/include/asm/atomic.h
@@ -28,8 +28,7 @@
* atomic_read - read atomic variable
* @v: pointer of type atomic_t
*
- * Atomically reads the value of @v. Note that the guaranteed
- * useful range of an atomic_t is only 24 bits.
+ * Atomically reads the value of @v.
*/
#define atomic_read(v) ((v)->counter)
@@ -38,8 +37,7 @@
* @v: pointer of type atomic_t
* @i: required value
*
- * Atomically sets the value of @v to @i. Note that the guaranteed
- * useful range of an atomic_t is only 24 bits.
+ * Atomically sets the value of @v to @i.
*/
#define atomic_set(v, i) (((v)->counter) = (i))
@@ -51,7 +49,6 @@
* @v: pointer of type atomic_t
*
* Atomically adds @i to @v and returns the result
- * Note that the guaranteed useful range of an atomic_t is only 24 bits.
*/
static inline int atomic_add_return(int i, atomic_t *v)
{
@@ -73,7 +70,6 @@ static inline int atomic_add_return(int i, atomic_t *v)
* @v: pointer of type atomic_t
*
* Atomically subtracts @i from @v and returns the result
- * Note that the guaranteed useful range of an atomic_t is only 24 bits.
*/
static inline int atomic_sub_return(int i, atomic_t *v)
{
--
1.7.1
next reply other threads:[~2010-04-28 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 10:50 Peter Fritzsche [this message]
2010-04-28 11:10 ` [PATCH 2/2] asm-generic: " Peter Fritzsche
2010-04-28 13:33 ` Arnd Bergmann
2010-04-28 13:54 ` Mathieu Desnoyers
2010-04-28 15:28 ` Jamie Lokier
2010-04-28 16:27 ` Mathieu Desnoyers
2010-04-28 18:42 ` Peter Fritzsche
2010-04-29 16:22 ` David Howells
2010-04-29 21:10 ` Mathieu Desnoyers
2010-04-30 8:53 ` Peter Fritzsche
2010-04-28 16:46 ` David Miller
2010-04-28 13:22 ` [PATCH 1/2] mn10300: " David Howells
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=1272451837-17961-1-git-send-email-peter.fritzsche@gmx.de \
--to=peter.fritzsche@gmx.de \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=remis.developer@googlemail.com \
--cc=wesolows@foobazco.org \
--cc=yasutake.koichi@jp.panasonic.com \
/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
all inboxes | Powered by JetHome®