From: Trevor Woerner <mips081@vtnet.ca>
To: tor@spacetec.no (Tor Arntsen), linux-mips@linux-mips.org
Subject: Re: 64-bit sysinfo
Date: Thu, 12 Jun 2003 08:04:47 -0400 [thread overview]
Message-ID: <200306120804.47827.mips081@vtnet.ca> (raw)
In-Reply-To: <200306121119.h5CBJWqC027855@pallas.spacetec.no>
On June 12, 2003 07:19 am, Tor Arntsen wrote:
> Hm, that sounds wrong to me. 'int' is supposed to be 32 bits also on
> 64-bit systems, only 'long' should be 64 bits.
Right, sorry. That was suppsed to read long. In any case, I put 'printk'
where the calls are being made as printed out the sizeof() of the
values and discovered that in user space they're 32 bits and in the
kernel they're 64 bits.
Trevor
WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <mips081@vtnet.ca>
To: Tor Arntsen <tor@spacetec.no>, linux-mips@linux-mips.org
Subject: Re: 64-bit sysinfo
Date: Thu, 12 Jun 2003 08:04:47 -0400 [thread overview]
Message-ID: <200306120804.47827.mips081@vtnet.ca> (raw)
Message-ID: <20030612120447.8wozVi97v6EJBKL6ury6ksyqI0ip-bhKBBaJ7mCTZhE@z> (raw)
In-Reply-To: <200306121119.h5CBJWqC027855@pallas.spacetec.no>
On June 12, 2003 07:19 am, Tor Arntsen wrote:
> Hm, that sounds wrong to me. 'int' is supposed to be 32 bits also on
> 64-bit systems, only 'long' should be 64 bits.
Right, sorry. That was suppsed to read long. In any case, I put 'printk'
where the calls are being made as printed out the sizeof() of the
values and discovered that in user space they're 32 bits and in the
kernel they're 64 bits.
Trevor
next prev parent reply other threads:[~2003-06-12 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 11:19 64-bit sysinfo Tor Arntsen
2003-06-12 12:04 ` Trevor Woerner [this message]
2003-06-12 12:04 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 10:59 Trevor Woerner
2003-06-12 11:35 ` Ralf Baechle
2003-06-12 12:07 ` Trevor Woerner
2003-06-12 12:27 ` Ralf Baechle
2003-06-12 21:36 ` Andrew Clausen
2003-06-12 11:44 ` Ralf Baechle
2003-06-12 12:02 ` Trevor Woerner
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=200306120804.47827.mips081@vtnet.ca \
--to=mips081@vtnet.ca \
--cc=linux-mips@linux-mips.org \
--cc=tor@spacetec.no \
/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