From: "Kip Walker" <kwalker@broadcom.com>
To: linux-mips@linux-mips.org
Subject: n32 signal stuff
Date: Mon, 21 Jul 2003 15:28:15 -0700 [thread overview]
Message-ID: <3F1C68FF.58E4E94D@broadcom.com> (raw)
I've just checked in (with Ralf's approval) some changes for N32 signal
handling that came up as 64-bit tool and glibc support evolved in the
last few months. Both 2.4 and 2.5/2.6 versions are there, but 2.4 has
had much more testing.
Credit where credit is due: this code was worked on by Chris Demetriou
and I just helped massage it into the public tree.
Hopefully there are no major complaints with this, although minor tweaks
are expected :-)
Kip
reply other threads:[~2003-07-21 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F1C68FF.58E4E94D@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@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.