mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-25 06:03:36 -04:00
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>
This commit is contained in:
parent
5518b69b76
commit
b4b8cbf679
1 changed files with 0 additions and 1 deletions
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue