Steven Rostedt bf5d770bd2 init: Do not warn on non-zero initcall return ... Commit f91eb62f71 ("init: scream bloody murder if interrupts are enabled too early") added three new warnings. The first two seemed reasonable, but the third included a warning when an initcall returned non-zero. Although, the third WARN() does include an imbalanced preempt disabled, or irqs disable, it shouldn't warn if it only had an initcall that just returns non-zero. In fact, according to Linus, it shouldn't print at all. As it only prints with initcall_debug set, and that already shows enough information to fix things. Link: http://lkml.kernel.org/r/CA+55aFzaBC5SFi7=F2mfm+KWY5qTsBmOqgbbs8E+LUS8JK-sBg@mail.gmail.com Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Reported-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2013-05-01 10:44:24 -07:00
..
calibrate.c
do_mounts_initrd.c	usermodehelper: split remaining calls to call_usermodehelper_fns()	2013-04-30 17:04:06 -07:00
do_mounts_md.c
do_mounts_rd.c
do_mounts.c
do_mounts.h
init_task.c
initramfs.c
Kconfig	init/Kconfig: re-order CONFIG_EXPERT options to fix menuconfig display	2013-04-30 17:04:09 -07:00
main.c	init: Do not warn on non-zero initcall return	2013-05-01 10:44:24 -07:00
Makefile
noinitramfs.c
version.c