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