From: Justin Chen <jchen@hpdst41.cup.hp.com>
To: linux-arch@vger.kernel.org
Cc: bjorn.helgaas@hp.com, justin.chen@hp.com,
linux-kernel@vger.kernel.org, takata@linux-m32r.org
Subject: [PATCH 15/15] bitops: Change the bitmap index from int to unsigned long [m32r]
Date: Tue, 24 Feb 2009 20:52:53 -0800 (PST) [thread overview]
Message-ID: <200902250452.UAA12910@hpdst41.cup.hp.com> (raw)
Change the index to unsigned long in all bitops for [m32r]
Signed-off-by: Justin Chen <justin.chen@hp.com>
Reviewed-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
---
include/asm-m32r/bitops.h | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff -Nru a/include/asm-m32r/bitops.h b/include/asm-m32r/bitops.h
--- a/include/asm-m32r/bitops.h 2009-02-13 15:31:30.000000000 -0800
+++ b/include/asm-m32r/bitops.h 2009-02-15 18:19:39.793041022 -0800
@@ -39,7 +39,7 @@
* Note that @nr may be almost arbitrarily large; this function is not
* restricted to acting on a single-word quantity.
*/
-static __inline__ void set_bit(int nr, volatile void * addr)
+static __inline__ void set_bit(unsigned long nr, volatile void *addr)
{
__u32 mask;
volatile __u32 *a = addr;
@@ -75,7 +75,7 @@
* you should call smp_mb__before_clear_bit() and/or smp_mb__after_clear_bit()
* in order to ensure changes are visible on other processors.
*/
-static __inline__ void clear_bit(int nr, volatile void * addr)
+static __inline__ void clear_bit(unsigned long nr, volatile void *addr)
{
__u32 mask;
volatile __u32 *a = addr;
@@ -114,7 +114,7 @@
* Note that @nr may be almost arbitrarily large; this function is not
* restricted to acting on a single-word quantity.
*/
-static __inline__ void change_bit(int nr, volatile void * addr)
+static __inline__ void change_bit(unsigned long nr, volatile void *addr)
{
__u32 mask;
volatile __u32 *a = addr;
@@ -148,7 +148,7 @@
* This operation is atomic and cannot be reordered.
* It also implies a memory barrier.
*/
-static __inline__ int test_and_set_bit(int nr, volatile void * addr)
+static __inline__ int test_and_set_bit(unsigned long nr, volatile void *addr)
{
__u32 mask, oldbit;
volatile __u32 *a = addr;
@@ -183,7 +183,8 @@
* This operation is atomic and cannot be reordered.
* It also implies a memory barrier.
*/
-static __inline__ int test_and_clear_bit(int nr, volatile void * addr)
+static __inline__ int
+test_and_clear_bit(unsigned long nr, volatile void *addr)
{
__u32 mask, oldbit;
volatile __u32 *a = addr;
@@ -220,7 +221,8 @@
* This operation is atomic and cannot be reordered.
* It also implies a memory barrier.
*/
-static __inline__ int test_and_change_bit(int nr, volatile void * addr)
+static __inline__ int
+test_and_change_bit(unsigned long nr, volatile void *addr)
{
__u32 mask, oldbit;
volatile __u32 *a = addr;
reply other threads:[~2009-02-25 4:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200902250452.UAA12910@hpdst41.cup.hp.com \
--to=jchen@hpdst41.cup.hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=justin.chen@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takata@linux-m32r.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
all inboxes | Powered by JetHome®