linux/drivers/crypto/cavium/nitrox
Linus Torvalds b4b8cbf679 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>
2017-07-05 13:03:05 -07:00
..
Kconfig Cavium CNN55XX: fix broken default Kconfig entry 2017-07-05 13:03:05 -07:00
Makefile crypto: cavium - Register the CNN55XX supported crypto algorithms. 2017-06-10 12:04:34 +08:00
nitrox_algs.c crypto: cavium - Register the CNN55XX supported crypto algorithms. 2017-06-10 12:04:34 +08:00
nitrox_common.h crypto: cavium - Register the CNN55XX supported crypto algorithms. 2017-06-10 12:04:34 +08:00
nitrox_csr.h
nitrox_dev.h
nitrox_hal.c
nitrox_isr.c
nitrox_lib.c crypto: cavium - Register the CNN55XX supported crypto algorithms. 2017-06-10 12:04:34 +08:00
nitrox_main.c crypto: cavium - fix spelling mistake "Revsion" -> "Revision" 2017-06-20 11:21:31 +08:00
nitrox_req.h
nitrox_reqmgr.c crypto: cavium/nitrox - dma_mapping_error() returns bool 2017-06-22 16:54:08 +08:00