summaryrefslogtreecommitdiffstats
path: root/arch/m68k/include/asm
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert@linux-m68k.org>2013-12-01 11:14:51 +0100
committerGeert Uytterhoeven <geert@linux-m68k.org>2013-12-08 11:03:21 +0100
commit8a09cec25fa19a3a7e9f21b4186fecc69085a60f (patch)
tree09099f3d883d9e8736e8ba363ffc79560038a976 /arch/m68k/include/asm
parentc6188d0f5756e3b20c216483cc7982d097c7b9de (diff)
downloadlinux-stable-8a09cec25fa19a3a7e9f21b4186fecc69085a60f.tar.gz
linux-stable-8a09cec25fa19a3a7e9f21b4186fecc69085a60f.tar.bz2
linux-stable-8a09cec25fa19a3a7e9f21b4186fecc69085a60f.zip
m68k/amiga,atari: Fix specifying multiple debug= parameters
Since commit d6713b4091a99fa2af2fabdcd2f3fb97f32ecf2e ("m68k: early parameter support"), the user can specify multiple debug consoles using the "debug=" kernel command line parameter. However, as there's only a single struct console object, which is reused, it would actually register the same console object multiple times, causing the following warning: WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233 register_console+0x36/ console 'debug0' already registered Make sure to register the console object only once, to avoid the warning. Note that still only one console (the one corresponding to the last "debug=" parameter) will be active at the same time, as the .write() method of the already registered console object is overwritten by a subsequent "debug=" parameter. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'arch/m68k/include/asm')
0 files changed, 0 insertions, 0 deletions