From: Richard Henderson <rth@twiddle.net>
To: "David S. Miller" <davem@redhat.com>
Cc: csr21@cam.ac.uk, linux-kernel@vger.kernel.org
Subject: Re: SPARC and SA_SIGINFO signal handling
Date: Sat, 3 Nov 2001 11:59:00 -0800 [thread overview]
Message-ID: <20011103115900.B5984@twiddle.net> (raw)
In-Reply-To: <20011029190027.A21372@cam.ac.uk> <20011030.125134.93645850.davem@redhat.com> <20011031094342.A27520@cam.ac.uk> <20011031.021131.74751566.davem@redhat.com>
In-Reply-To: <20011031.021131.74751566.davem@redhat.com>; from davem@redhat.com on Wed, Oct 31, 2001 at 02:11:31AM -0800
On Wed, Oct 31, 2001 at 02:11:31AM -0800, David S. Miller wrote:
> The "register contents and so on" are in the sigcontext.
> We don't use ucontext on sparc32.
In other words, you don't support SA_SIGINFO at all.
r~
next prev parent reply other threads:[~2001-11-03 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 19:00 SPARC and SA_SIGINFO signal handling Christophe Rhodes
2001-10-30 20:51 ` David S. Miller
2001-10-31 9:43 ` Christophe Rhodes
2001-10-31 10:11 ` David S. Miller
2001-11-03 19:59 ` Richard Henderson [this message]
2001-11-03 23:54 ` David S. Miller
2001-11-04 17:25 ` Richard Henderson
2001-11-07 9:33 ` Christophe Rhodes
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=20011103115900.B5984@twiddle.net \
--to=rth@twiddle.net \
--cc=csr21@cam.ac.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).