From: Adrian Bunk <bunk@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Bryan Wu <cooloney.lkml@gmail.com>
Subject: [2.6 patch] make BINFMT_FLAT a bool
Date: Sun, 20 Jan 2008 21:20:19 +0200 [thread overview]
Message-ID: <20080120192019.GH8669@does.not.exist> (raw)
I have not yet seen anyone saying he has a reasonable use case for using
BINFMT_FLAT modular on his embedded device.
Considering that fs/binfmt_flat.c even lacks a MODULE_LICENSE() I really
doubt there is any, and this patch therefore makes BINFMT_FLAT a bool.
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Acked-by: Bryan Wu <cooloney.lkml@gmail.com>
---
This patch has been sent on:
- 1 Jan 2008
fs/Kconfig.binfmt | 2 +-
fs/binfmt_flat.c | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
5437fb7517380d1b93dde3c09dbd3a2efaf276c3
diff --git a/fs/Kconfig.binfmt b/fs/Kconfig.binfmt
index d4fc609..c16a16c 100644
--- a/fs/Kconfig.binfmt
+++ b/fs/Kconfig.binfmt
@@ -37,7 +37,7 @@ config BINFMT_ELF_FDPIC
It is also possible to run FDPIC ELF binaries on MMU linux also.
config BINFMT_FLAT
- tristate "Kernel support for flat binaries"
+ bool "Kernel support for flat binaries"
depends on !MMU
help
Support uClinux FLAT format binaries.
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 33764fd..274d723 100644
--- a/fs/binfmt_flat.c
+++ b/fs/binfmt_flat.c
@@ -933,14 +933,8 @@ static int __init init_flat_binfmt(void)
return register_binfmt(&flat_format);
}
-static void __exit exit_flat_binfmt(void)
-{
- unregister_binfmt(&flat_format);
-}
-
/****************************************************************************/
core_initcall(init_flat_binfmt);
-module_exit(exit_flat_binfmt);
/****************************************************************************/
next reply other threads:[~2008-01-20 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 19:20 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 21:31 [2.6 patch] make BINFMT_FLAT a bool Adrian Bunk
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=20080120192019.GH8669@does.not.exist \
--to=bunk@kernel.org \
--cc=cooloney.lkml@gmail.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 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.