summaryrefslogtreecommitdiffstats
path: root/drivers/staging/unisys/Kconfig
diff options
context:
space:
mode:
authorKen Cox <jkc@redhat.com>2014-06-26 09:55:56 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-06-26 20:16:39 -0400
commitd93b88eb7628fc70f7e0feef640132bb484b70ef (patch)
tree8660ee2652663f07dfb1267e4adb9f58b4239e91 /drivers/staging/unisys/Kconfig
parent836bee9eee6d13cb4f3bf2a53133fab576877dac (diff)
downloadop-kernel-dev-d93b88eb7628fc70f7e0feef640132bb484b70ef.zip
op-kernel-dev-d93b88eb7628fc70f7e0feef640132bb484b70ef.tar.gz
Staging: unisys Remove BROKEN from Kconfig to allow compilation
The unisys drivers now properly check to make sure they are running on the s-Par platform before they will initialize. This was fixed in commit fcd0157ece so it is safe to allow the unisys drivers to be built. This has been tested in the same qemu environment that originally produced the panic and the kernel now runs as expected. Reported-by: Fengguang Wu <fengguang.wu@intel.com> Reported-by: Sasha Levin <sasha.levin@oracle.com> Tested-by: Ken Cox <jkc@redhat.com> Signed-off-by: Ken Cox <jkc@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/unisys/Kconfig')
-rw-r--r--drivers/staging/unisys/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/staging/unisys/Kconfig b/drivers/staging/unisys/Kconfig
index 6bae2af..ac080c9 100644
--- a/drivers/staging/unisys/Kconfig
+++ b/drivers/staging/unisys/Kconfig
@@ -3,7 +3,7 @@
#
menuconfig UNISYSSPAR
bool "Unisys SPAR driver support"
- depends on X86_64 && BROKEN
+ depends on X86_64
---help---
Support for the Unisys SPAR drivers
OpenPOWER on IntegriCloud