From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.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 16:41:07 +0000 [thread overview]
Message-ID: <20070313164107.GA5004@linux-mips.org> (raw)
In-Reply-To: <20070313141951.GA3206@caradoc.them.org>
On Tue, Mar 13, 2007 at 10:19:51AM -0400, Daniel Jacobowitz wrote:
> 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.
Yes, you're right. Will you cook up a patch?
Ralf
next prev parent reply other threads:[~2007-03-13 16:43 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
2007-03-13 16:41 ` Ralf Baechle [this message]
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=20070313164107.GA5004@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=pwatkins@sicortex.com \
/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