From: Adrian Bunk <bunk@stusta.de>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] mips: remove the broken BINFMT_IRIX code
Date: Thu, 4 Jan 2007 19:52:58 +0100 [thread overview]
Message-ID: <20070104185258.GD20714@stusta.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
The BINFMT_IRIX code:
- has been marked as BROKEN for more than two years years and
- is still marked as BROKEN.
Code that has been marked as BROKEN for such a long time seem to be
unlikely to be revived in the forseeable future.
But if anyone wants to ever revive this driver, the code is still
present in the older kernel releases.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Due to it's size, the patch is attached compressed.
arch/mips/Kconfig | 4
arch/mips/kernel/Makefile | 4
arch/mips/kernel/irix5sys.S | 1041 ----------------
arch/mips/kernel/irixelf.c | 1332 --------------------
arch/mips/kernel/irixinv.c | 78 -
arch/mips/kernel/irixioctl.c | 251 ---
arch/mips/kernel/irixsig.c | 880 -------------
arch/mips/kernel/process.c | 7
arch/mips/kernel/scall32-o32.S | 18
arch/mips/kernel/sysirix.c | 2140 ---------------------------------
include/asm-mips/signal.h | 3
11 files changed, 5758 deletions(-)
[-- Attachment #2: patch-remove-BINFMT_IRIX.gz --]
[-- Type: application/octet-stream, Size: 34260 bytes --]
next reply other threads:[~2007-01-04 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 18:52 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-20 14:01 [RFC: 2.6 patch] mips: remove the broken BINFMT_IRIX code Adrian Bunk
2007-01-20 14:39 ` Ralf Baechle
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=20070104185258.GD20714@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox