Browse Source

Use menuconfig objects: connector

Use menuconfigs instead of menus, so the whole menu can be disabled at once
instead of going through all options.

Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
Acked-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Jan Engelhardt 18 years ago
parent
commit
13591885a9
1 changed files with 4 additions and 3 deletions
  1. 4 3
      drivers/connector/Kconfig

+ 4 - 3
drivers/connector/Kconfig

@@ -1,6 +1,5 @@
-menu "Connector - unified userspace <-> kernelspace linker"
 
 
-config CONNECTOR
+menuconfig CONNECTOR
 	tristate "Connector - unified userspace <-> kernelspace linker"
 	tristate "Connector - unified userspace <-> kernelspace linker"
 	depends on NET
 	depends on NET
 	---help---
 	---help---
@@ -10,6 +9,8 @@ config CONNECTOR
 	  Connector support can also be built as a module.  If so, the module
 	  Connector support can also be built as a module.  If so, the module
 	  will be called cn.ko.
 	  will be called cn.ko.
 
 
+if CONNECTOR
+
 config PROC_EVENTS
 config PROC_EVENTS
 	boolean "Report process events to userspace"
 	boolean "Report process events to userspace"
 	depends on CONNECTOR=y
 	depends on CONNECTOR=y
@@ -18,4 +19,4 @@ config PROC_EVENTS
 	  Provide a connector that reports process events to userspace. Send
 	  Provide a connector that reports process events to userspace. Send
 	  events such as fork, exec, id change (uid, gid, suid, etc), and exit.
 	  events such as fork, exec, id change (uid, gid, suid, etc), and exit.
 
 
-endmenu
+endif # CONNECTOR