Skip to content

Commit

Permalink
driver core: Make Kconfig text for DEBUG_TEST_DRIVER_REMOVE stronger
Browse files Browse the repository at this point in the history
The current state of driver removal is not great.
CONFIG_DEBUG_TEST_DRIVER_REMOVE finds lots of errors. The help text
currently undersells exactly how many errors this option will find. Add
a bit more description to indicate this option shouldn't be turned on
unless you actually want to debug driver removal. The text can be
changed later when more drivers are fixed up.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  • Loading branch information
Laura Abbott authored and Greg Kroah-Hartman committed Oct 27, 2016
1 parent 2a9becd commit 248ff02
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions drivers/base/Kconfig
Original file line number Diff line number Diff line change
Expand Up @@ -213,14 +213,16 @@ config DEBUG_DEVRES
If you are unsure about this, Say N here.

config DEBUG_TEST_DRIVER_REMOVE
bool "Test driver remove calls during probe"
bool "Test driver remove calls during probe (UNSTABLE)"
depends on DEBUG_KERNEL
help
Say Y here if you want the Driver core to test driver remove functions
by calling probe, remove, probe. This tests the remove path without
having to unbind the driver or unload the driver module.

If you are unsure about this, say N here.
This option is expected to find errors and may render your system
unusable. You should say N here unless you are explicitly looking to
test this functionality.

config SYS_HYPERVISOR
bool
Expand Down

0 comments on commit 248ff02

Please sign in to comment.