Luis R. Rodriguez 27d5d7dc9a firmware_loader: make firmware_fallback_sysfs() print more useful ... If we resort to using the sysfs fallback mechanism we don't print the filename. This can be deceiving given we could have a series of callers intertwined and it'd be unclear exactly for what firmware this was meant for. Additionally, although we don't currently use FW_OPT_NO_WARN when dealing with the fallback mechanism, we will soon, so just respect its use consistently. And even if you *don't* want to print always on failure, you may want to print when debugging so enable dynamic debug print when FW_OPT_NO_WARN is used. Reviewed-by: Kees Cook <keescook@chromium.org> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2018-05-14 16:43:10 +02:00
..
fallback_table.c	firmware: enable to force disable the fallback mechanism at run time	2018-03-20 09:28:47 +01:00
fallback.c	firmware_loader: make firmware_fallback_sysfs() print more useful	2018-05-14 16:43:10 +02:00
fallback.h	firmware: rename fw_sysfs_fallback to firmware_fallback_sysfs()	2018-05-14 16:43:09 +02:00
firmware.h	firmware: rename fw_sysfs_fallback to firmware_fallback_sysfs()	2018-05-14 16:43:09 +02:00
Kconfig	firmware_loader: move kconfig FW_LOADER entries to its own file	2018-05-14 16:43:10 +02:00
main.c	firmware: rename fw_sysfs_fallback to firmware_fallback_sysfs()	2018-05-14 16:43:09 +02:00
Makefile	firmware: move firmware loader into its own directory	2018-03-20 09:28:46 +01:00