From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Subject: incompatable pointer type warnings on some archs
Date: 11 Dec 2002 00:48:26 -0500 [thread overview]
Message-ID: <m37kehm7h1.fsf@lugabout.jhcloos.org> (raw)
I see that find_next_zero_bit() has a first arg of void* in about half
of the archs and unsigned long* in the rest (incl asm-i386/bitops.h).
Looking at incompatable pointer type warnings in a recent compile, I
found one where the caller was passing a u64*, thus the error.
Should all of the archs use a void* for this, or is there some reason
not to?
test_and_set_bit() and test_and_clear_bit() also have the same issue.
-JimC
reply other threads:[~2002-12-11 5:40 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=m37kehm7h1.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--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 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.