From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] bogus __clear_bit macro
Date: Tue, 11 Mar 2003 22:37:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806037@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806025@msgid-missing>
>>>>> "Kenneth" = Kenneth W Chen <Chen> writes:
Kenneth> David,
Kenneth> It looks like when __clear_bit() was implemented, the deletion of the macro falls through the crack. This macro prohibit the actual __clear_bit to be invoked.
While you're fixing bitops.h, making test_bit take a const qualified
arg will kill some warnings in reiserfs...
--- /tmp/geta24522 2003-03-12 09:19:31.000000000 +1100
+++ linux/include/asm-ia64/bitops.h 2003-03-12 09:17:53.000000000 +1100
@@ -275,7 +275,7 @@
}
static __inline__ int
-test_bit (int nr, volatile void *addr)
+test_bit (int nr, const volatile void *addr)
{
return 1 & (((const volatile __u32 *) addr)[nr >> 5] >> (nr & 31));
}
prev parent reply other threads:[~2003-03-11 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 19:01 [Linux-ia64] bogus __clear_bit macro Chen, Kenneth W
2003-03-11 22:37 ` Peter Chubb [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=marc-linux-ia64-105590709806037@msgid-missing \
--to=peter@chubb.wattle.id.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox