diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2017-07-05 13:03:05 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-07-05 13:03:05 -0700 |
| commit | b4b8cbf679c4866a523a35d1454884a31bd5d8dc (patch) | |
| tree | 9e0b564c7ba98296bdc558494f37afea353daf66 /drivers/crypto/cavium | |
| parent | 5518b69b76680a4f2df96b1deca260059db0c2de (diff) | |
| download | linux-b4b8cbf679c4866a523a35d1454884a31bd5d8dc.tar.gz linux-b4b8cbf679c4866a523a35d1454884a31bd5d8dc.tar.bz2 linux-b4b8cbf679c4866a523a35d1454884a31bd5d8dc.zip | |
Cavium CNN55XX: fix broken default Kconfig entry
Every developer always thinks that _their_ code is so special and
magical that it should be enabled by default.
And most of them are completely and utterly wrong. That's definitely
the case when you write a specialty driver for a very unsual "security
processor". It does *not* get to mark itself as "default m".
If you solve world hunger, and make a driver that cures people of
cancer, by all means enable it by default. But afaik, the Cavium
CNN55XX does neither.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/crypto/cavium')
| -rw-r--r-- | drivers/crypto/cavium/nitrox/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/crypto/cavium/nitrox/Kconfig b/drivers/crypto/cavium/nitrox/Kconfig index 731e6a57218a..181a1dfec932 100644 --- a/drivers/crypto/cavium/nitrox/Kconfig +++ b/drivers/crypto/cavium/nitrox/Kconfig @@ -12,7 +12,6 @@ config CRYPTO_DEV_NITROX_CNN55XX tristate "Support for Cavium CNN55XX driver" depends on PCI_MSI && 64BIT select CRYPTO_DEV_NITROX - default m help Support for Cavium NITROX family CNN55XX driver for accelerating crypto workloads. |