From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Peter Watkins <pwatkins@sicortex.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Have sigpoll and sigio band field match glibc for n64
Date: Tue, 13 Mar 2007 10:19:51 -0400 [thread overview]
Message-ID: <20070313141951.GA3206@caradoc.them.org> (raw)
In-Reply-To: <20070310132423.GA1295@linux-mips.org>
On Sat, Mar 10, 2007 at 01:24:24PM +0000, Ralf Baechle wrote:
> On Fri, Mar 09, 2007 at 02:46:25PM -0500, Peter Watkins wrote:
>
> > The siginfo field si_fd is incorrect on n64 because the band field does
> > not match glibc.
>
> Susv3 says:
>
> [...]
> The <signal.h> header shall define the siginfo_t type as a structure that
> includes at least the following members:
>
> [...]
> long si_band Band event for SIGPOLL.
> [...]
>
> So the kernel is right, glibc is wrong I'd say ...
This will break the ABI only for uses of si_band and si_fd, and only
on n64. Anyone see a reason why I shouldn't change glibc?
Ralf, as I mentioned on IRC, I've got bigger worries about siginfo.
Shouldn't n32 be using the same siginfo as o32? It's got pointers in it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-13 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 19:46 [PATCH] Have sigpoll and sigio band field match glibc for n64 Peter Watkins
2007-03-09 19:46 ` Peter Watkins
2007-03-10 13:24 ` Ralf Baechle
2007-03-13 14:19 ` Daniel Jacobowitz [this message]
2007-03-13 16:41 ` Ralf Baechle
2007-03-14 17:48 ` Daniel Jacobowitz
2007-03-14 17:56 ` Ralf Baechle
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=20070313141951.GA3206@caradoc.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=pwatkins@sicortex.com \
--cc=ralf@linux-mips.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 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.