From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: different xxx_bit() function prototypes in bitops for x86 vs generic
Date: Thu, 9 Mar 2017 17:11:22 +0000 [thread overview]
Message-ID: <1489079480.4533.12.camel@infinera.com> (raw)
Building virtualbox external kernel modules warns about different types, example:
include/asm-generic/bitops/le.h;
set_bit_le(int nr, const void *addr)
vs
arch/x86/include/asm/bitops.h:
set_bit(long nr, volatile unsigned long *addr)
This difference is causes complaints, changing
set_bit_le(int nr, const void *addr)
to
set_bit_le(int nr, const unsigned long *addr)
makes the warnings go away for this function.
Should not these two be the same?
reply other threads:[~2017-03-09 17:11 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=1489079480.4533.12.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=akpm@linux-foundation.org \
--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 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®