blob: 7fdcafa62d9d7e2bc69d4b0315c23524a8d7c01d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
From de6299c1627d80ea6742a0bef15bdb6981e5cfd7 Mon Sep 17 00:00:00 2001
From: Nikolay Amiantov <ab@fmap.me>
Date: Fri, 25 Dec 2015 17:11:40 +0300
Subject: [PATCH 1/2] drivers_base: fix double Kconfig entry
---
drivers/base/Kconfig | 24 ------------------------
1 file changed, 24 deletions(-)
diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index 946ced4..fc3405e1 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -163,30 +163,6 @@ config FW_LOADER_USER_HELPER
no longer required unless you have a special firmware file that
resides in a non-standard path.
-config WANT_DEV_COREDUMP
- bool
- help
- Drivers should "select" this option if they desire to use the
- device coredump mechanism.
-
-config ALLOW_DEV_COREDUMP
- bool "Allow device coredump" if EXPERT
- default y
- help
- This option controls if the device coredump mechanism is available or
- not; if disabled, the mechanism will be omitted even if drivers that
- can use it are enabled.
- Say 'N' for more sensitive systems or systems that don't want
- to ever access the information to not have the code, nor keep any
- data.
-
- If unsure, say Y.
-
-config DEV_COREDUMP
- bool
- default y if WANT_DEV_COREDUMP
- depends on ALLOW_DEV_COREDUMP
-
config DEBUG_DRIVER
bool "Driver Core verbose debug messages"
depends on DEBUG_KERNEL
--
2.6.3
|