From: Jakub Jelinek <jakub@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kurt Roeckx <Q@ping.be>, linux-kernel@vger.kernel.org
Subject: Re: siginfo pad problem.
Date: Tue, 22 Jul 2003 13:19:40 -0400 [thread overview]
Message-ID: <20030722131940.W15481@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030722095105.5ed2379a.sfr@canb.auug.org.au>; from sfr@canb.auug.org.au on Tue, Jul 22, 2003 at 09:51:05AM +1000
On Tue, Jul 22, 2003 at 09:51:05AM +1000, Stephen Rothwell wrote:
> Anywhere this should be used (i.e. only in the kernel), uid_t will be
> __kernel_uid32_t. The change to this part of the siginfo_t structure has
> not yet propogated to the glibc headers and when it does, it is up to the
> glibc maintainers to make sure it matches what is used inside the kernel.
??
glibc uses <bits/siginfo.h>, in which it uses __uid_t for si_uid fields.
__uid_t is uint32_t on all arches.
Jakub
prev parent reply other threads:[~2003-07-22 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 14:23 siginfo pad problem Kurt Roeckx
2003-07-21 16:24 ` Stephen Rothwell
2003-07-21 18:00 ` Kurt Roeckx
2003-07-21 23:51 ` Stephen Rothwell
2003-07-22 17:06 ` Kurt Roeckx
2003-07-22 17:14 ` Jamie Lokier
2003-07-22 17:19 ` Jakub Jelinek [this message]
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=20030722131940.W15481@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Q@ping.be \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.