From: Ralf Baechle <ralf@linux-mips.org>
To: Mika Kukkonen <mika@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-mips@linux-mips.org
Subject: Re: MIPS defines __kernel_uid_t as int?
Date: Thu, 8 Jul 2004 02:59:45 +0200 [thread overview]
Message-ID: <20040708005945.GA17133@linux-mips.org> (raw)
In-Reply-To: <1089223996.20452.31.camel@miku.mobile.lnx.nokia.com>
On Wed, Jul 07, 2004 at 11:13:16AM -0700, Mika Kukkonen wrote:
> I was doing
> $ grep __kernel_uid_t include/*/posix_types.h
>
> and noticed that MIPS is the only architecture that
> defines that to be signed (int) and not unsigned?
>
> Same with __kernel_uid32_t. Is this intentional
> deviation or just an oversight?
Intentional but with a really weak reason. Linux/MIPS uses the same
type definitions as SysV rsp. the MIPS ABI in it's EFT (Extended
Fundamental Types). Not a great idea in retroperspective but that's a
choice made 10 years ago.
I don't think we'd break anything by changing this. Objections to
changing it?
Ralf
parent reply other threads:[~2004-07-08 0:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1089223996.20452.31.camel@miku.mobile.lnx.nokia.com>]
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=20040708005945.GA17133@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@osdl.org \
--cc=linux-mips@linux-mips.org \
--cc=mika@osdl.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