From: Michal Kochanowicz <michal@michal.waw.pl>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test6] definition and usage of __u64/__s64 inconsistent?
Date: Fri, 3 Oct 2003 10:54:12 +0200 [thread overview]
Message-ID: <20031003085412.GA4602@wieszak.lan> (raw)
Hi!
The two types are _conditionally_ defined as follows (in asm/types.h):
#if defined(__GNUC__) && !defined(__STRICT_ANSI__)
typedef __signed__ long long __s64;
typedef unsigned long long __u64;
#endif
The file asm/types.h is _unconditionally_ included from linux/cdrom.h
and linux/loop.h and both files use __u64 unonditionally. Isn't this an
error?
Regards
PS. I came across this problem while trying to compile
kdemultimedia-3.1.4 which uses linux/linux.h - if it does matter.
--
--= Michal Kochanowicz =--==--==BOFH==--==--= michal@michal.waw.pl =--
--= finger me for PGP public key or visit http://michal.waw.pl/PGP =--
--==--==--==--==--==-- Vodka. Connecting people.--==--==--==--==--==--
A chodzenie po górach SSIE!!!
next reply other threads:[~2003-10-03 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 8:54 Michal Kochanowicz [this message]
2003-10-03 9:03 ` [2.6.0-test6] definition and usage of __u64/__s64 inconsistent? David S. Miller
2003-10-03 18:12 ` Michal Kochanowicz
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=20031003085412.GA4602@wieszak.lan \
--to=michal@michal.waw.pl \
--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