From: Stephen Rothwell <sfr@canb.auug.org.au>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Consolidate include/asm/signal.h
Date: Thu, 20 Jun 2002 16:57:50 +1000 [thread overview]
Message-ID: <20020620165750.6d621e68.sfr@canb.auug.org.au> (raw)
[It occurred to me that this patch may not have made it to LKML due to
its size, so here it is with a URL]
Hi all,
Have I gone too far this time? :-)
This patch consolidates most of the common signal.h stuff between
architectures into include/asm-generic/signal.h. It builds fine
on i386, but may have broken all the other architectures despite
being careful.
Please test (at least a build) and/or comment.
http://www.canb.auug.org.au/~sfr/22-sfr.5.diff.gz
diffstat looks like this:
asm-alpha/signal.h | 62 --------------
asm-arm/signal.h | 128 ------------------------------
asm-cris/signal.h | 126 ------------------------------
asm-generic/signal.h | 212 +++++++++++++++++++++++++++++++++++++++++++++++++++
asm-i386/signal.h | 126 ------------------------------
asm-ia64/signal.h | 83 ++-----------------
asm-m68k/signal.h | 126 ------------------------------
asm-mips/signal.h | 46 +----------
asm-mips64/signal.h | 40 +--------
asm-parisc/signal.h | 72 ++++-------------
asm-ppc/signal.h | 100 ------------------------
asm-ppc64/signal.h | 96 -----------------------
asm-s390/signal.h | 104 -------------------------
asm-s390x/signal.h | 104 -------------------------
asm-sh/signal.h | 114 ---------------------------
asm-sparc/signal.h | 75 +++++-------------
asm-sparc64/signal.h | 72 ++++-------------
asm-x86_64/signal.h | 108 +------------------------
18 files changed, 326 insertions(+), 1468 deletions(-)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next reply other threads:[~2002-06-20 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 6:57 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 5:47 Stephen Rothwell
2002-06-18 6:21 ` Andi Kleen
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=20020620165750.6d621e68.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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
all inboxes | Powered by JetHome®