From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] bitop warnings
Date: Fri, 21 Jan 2005 21:50:59 +0000 [thread overview]
Message-ID: <20050121225808.GC11543@localhost.localdomain> (raw)
Hi Tony:
I don't believe this has been submitted. It removes many compiler warnings.
thanks,
bob
Signed-off-by: Bob Picco <bob.picco@hp.com>
diff -ruNp -X /home/picco/losl/dontdiff linux-2.6.11-rc1-mm1-mhp1-orig/arch/ia64/lib/bitop.c linux-2.6.11-rc1-mm1-mhp1/arch/ia64/lib/bitop.c
--- linux-2.6.11-rc1-mm1-mhp1-orig/arch/ia64/lib/bitop.c 2004-12-24 16:35:24.000000000 -0500
+++ linux-2.6.11-rc1-mm1-mhp1/arch/ia64/lib/bitop.c 2005-01-20 15:49:15.000000000 -0500
@@ -8,7 +8,7 @@
* Find next zero bit in a bitmap reasonably efficiently..
*/
-int __find_next_zero_bit (void *addr, unsigned long size, unsigned long offset)
+int __find_next_zero_bit (const void *addr, unsigned long size, unsigned long offset)
{
unsigned long *p = ((unsigned long *) addr) + (offset >> 6);
unsigned long result = offset & ~63UL;
diff -ruNp -X /home/picco/losl/dontdiff linux-2.6.11-rc1-mm1-mhp1-orig/include/asm-ia64/bitops.h linux-2.6.11-rc1-mm1-mhp1/include/asm-ia64/bitops.h
--- linux-2.6.11-rc1-mm1-mhp1-orig/include/asm-ia64/bitops.h 2004-12-24 16:35:28.000000000 -0500
+++ linux-2.6.11-rc1-mm1-mhp1/include/asm-ia64/bitops.h 2005-01-20 15:26:48.000000000 -0500
@@ -359,7 +359,7 @@ hweight64 (unsigned long x)
#endif /* __KERNEL__ */
-extern int __find_next_zero_bit (void *addr, unsigned long size,
+extern int __find_next_zero_bit (const void *addr, unsigned long size,
unsigned long offset);
extern int __find_next_bit(const void *addr, unsigned long size,
unsigned long offset);
reply other threads:[~2005-01-21 21:50 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=20050121225808.GC11543@localhost.localdomain \
--to=bob.picco@hp.com \
--cc=linux-ia64@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 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.