From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: siginfo difference MIPS and other arches
Date: Fri, 8 Oct 2010 16:58:23 +0100 [thread overview]
Message-ID: <20101008155823.GB30185@linux-mips.org> (raw)
In-Reply-To: <AANLkTimYGDoRovYgbReeBihD2nfYFHE_CmwJjv2_=s7v@mail.gmail.com>
On Fri, Oct 08, 2010 at 05:55:01PM +0200, Manuel Lauss wrote:
> >> current -git build breaks because of upstream commit
> >> a337fdac7a5622d1e6547f4b476c14dfe5a2c892, which introduced
> >> an unconditional check for siginfo_._sifields._sifault._si_addr_lsb field.
> >>
> >> Is there a reason why MIPS doesn't use the default siginfo_t structure
> >> as other architectures do?
> >
> > History - the MIPS structure is identical to IRIX.
>
> Does anyone still run IRIX binaries on current linux?
> (and Isn't IRIX dead anyway? :) )
Doesn't matter - you can't change the definition without breaking
binary compatibility.
Ralf
prev parent reply other threads:[~2010-10-08 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 14:16 siginfo difference MIPS and other arches Manuel Lauss
2010-10-08 15:53 ` Ralf Baechle
2010-10-08 15:55 ` Manuel Lauss
2010-10-08 15:58 ` Ralf Baechle [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=20101008155823.GB30185@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.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