From 8c69c9232ac4c6cb157b28803a69048475bccabf Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 4 Jul 2008 15:09:27 +0000
Subject: [PATCH] Note a few more architectures on which signal numbers are
 valid. SEE ALSO: added a number of pages.

---
 man7/signal.7 | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/man7/signal.7 b/man7/signal.7
index 4064d7405..ecd2c1d3a 100644
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -126,8 +126,10 @@ Linux supports the standard signals listed below.
 Several signal numbers
 are architecture-dependent, as indicated in the "Value" column.
 (Where three values are given, the first one is usually valid for
-alpha and sparc, the middle one for i386, ppc and sh, and
-the last one for mips.
+alpha and sparc,
+the middle one for ix86, ia64, ppc, s390, arm and sh,
+and the last one for mips.
+.\" parisc is a law unto itself
 A \- denotes that a signal is absent on the corresponding architecture.)
 
 First the signals described in the original POSIX.1-1990 standard.
@@ -666,12 +668,14 @@ signal 29 is
 .BR SIGLOST .
 .SH "SEE ALSO"
 .BR kill (1),
+.BR getrlimit (2),
 .BR kill (2),
 .BR killpg (2),
 .BR setitimer (2),
 .BR setrlimit (2),
 .BR sgetmask (2),
 .BR sigaction (2),
+.BR sigaltstack (2),
 .BR signal (2),
 .BR signalfd (2),
 .BR sigpending (2),
@@ -679,10 +683,14 @@ signal 29 is
 .BR sigqueue (2),
 .BR sigsuspend (2),
 .BR sigwaitinfo (2),
+.BR abort (3),
 .BR bsd_signal (3),
+.BR longjmp (3),
 .BR raise (3),
 .BR sigvec (3),
 .BR sigset (3),
+.BR sigsetops (3),
+.BR sigvec (3),
 .BR sigwait (3),
 .BR strsignal (3),
 .BR sysv_signal (3),