Driver core: fix 'dynamic_debug' cmd line parameter
authorJason Baron <jbaron@redhat.com>
Mon, 27 Oct 2008 16:05:14 +0000 (12:05 -0400)
committerGreg Kroah-Hartman <gregkh@suse.de>
Wed, 29 Oct 2008 22:03:50 +0000 (15:03 -0700)
commit113328306dbdfd5f146f257e447364dc66d025d4
treea62ad2388617b8e7943ed9133a582a3fcef7f0da
parent555ac6482ea7d0f29ec524b816f2f547ec94e882
Driver core: fix 'dynamic_debug' cmd line parameter

In testing 2.6.28-rc1, I found that passing 'dynamic_printk' on the command
line didn't activate the debug code. The problem is that dynamic_printk_setup()
(which activates the debugging) is being called before dynamic_printk_init() is
called (which initializes infrastructure). Fix this by setting setting the
state to 'DYNAMIC_ENABLED_ALL' in dynamic_printk_setup(), which will also
cause all subsequent modules to have debugging automatically started, which is
probably the behavior we want.

Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
lib/dynamic_printk.c