From: Thorsten Glaser <tg@debian.org>
To: linux-m68k@vger.kernel.org
Subject: [PATCH] make NatFeat drivers bool, not tristate
Date: Tue, 23 Jul 2013 22:51:45 +0000 [thread overview]
Message-ID: <201307232255.r6NMt8Z9027017@herc.mirbsd.org> (raw)
- nfblock: doesn't create /dev/nfhd8p1 device node after modprobe
- nfcon: is totally useless as module, almost only used during boot
- nfeth: says "No such device" upon insmod
Signed-off-by: Thorsten Glaser <tg@debian.org>
---
arch/m68k/Kconfig.devices | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/m68k/Kconfig.devices b/arch/m68k/Kconfig.devices
index d163991..a306c50 100644
--- a/arch/m68k/Kconfig.devices
+++ b/arch/m68k/Kconfig.devices
@@ -32,7 +32,7 @@ config NATFEAT
access to a disk image as /dev/hda.
config NFBLOCK
- tristate "NatFeat block device support"
+ bool "NatFeat block device support"
depends on BLOCK && NATFEAT
help
Say Y to include support for the ARAnyM NatFeat block device
@@ -40,7 +40,7 @@ config NFBLOCK
the hardware emulation.
config NFCON
- tristate "NatFeat console driver"
+ bool "NatFeat console driver"
depends on TTY && NATFEAT
help
Say Y to include support for the ARAnyM NatFeat console driver
@@ -48,7 +48,7 @@ config NFCON
output of ARAnyM.
config NFETH
- tristate "NatFeat Ethernet support"
+ bool "NatFeat Ethernet support"
depends on ETHERNET && NATFEAT
help
Say Y to include support for the ARAnyM NatFeat network device
--
1.7.9
next reply other threads:[~2013-07-23 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 22:51 Thorsten Glaser [this message]
2013-07-24 8:57 ` [PATCH] make NatFeat drivers bool, not tristate Andreas Schwab
2013-07-24 12:42 ` Thorsten Glaser
2013-07-24 13:26 ` Thorsten Glaser
2013-07-24 14:56 ` Geert Uytterhoeven
2013-07-24 15:02 ` Petr Stehlik
2013-07-24 16:19 ` Geert Uytterhoeven
2013-07-24 20:04 ` Petr Stehlik
2013-07-24 17:23 ` Thorsten Glaser
2013-07-24 17:40 ` Geert Uytterhoeven
2013-07-29 21:52 ` Geert Uytterhoeven
2013-07-30 8:50 ` Thorsten Glaser
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=201307232255.r6NMt8Z9027017@herc.mirbsd.org \
--to=tg@debian.org \
--cc=linux-m68k@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