From: "Carlos O'Donell" <carlos@baldric.uwo.ca>
To: linux-ia64@vger.kernel.org
Subject: [Q] Why is compat_uid_t a u16 value?
Date: Sun, 12 Sep 2004 15:01:09 +0000 [thread overview]
Message-ID: <20040912150108.GO1854@baldric.uwo.ca> (raw)
ia64-ml,
The ia32 emulation code is using 'unsigned int' for uid_t returned back
to userspace. While the compat.h definitions uses compat_uid_t, which
is defined as u16. Is this correct? I would assume that compat_uid_t
should be u32 under ia64.
Is there any reason it is currently defined as u16?
Is the compat.h definition of compat_uid_t ever used anywhere?
I'm testing some patches to cleanup compat code, but I noticed some
discrepancies in the ia64 definitions of compat.h.
Cheers,
Carlos.
next reply other threads:[~2004-09-12 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 15:01 Carlos O'Donell [this message]
2004-09-12 19:55 ` [Q] Why is compat_uid_t a u16 value? Chris Wedgwood
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=20040912150108.GO1854@baldric.uwo.ca \
--to=carlos@baldric.uwo.ca \
--cc=linux-ia64@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