Re: Locking API testsuite output mangled

On Wed, 23 Nov 2016, Michael Ellerman wrote: > That's nothing powerpc specific AFAICS, does this fix it? Hm, so s/printk/pr_cont/ - but not in all places? But yeah, this fixes it for me, at least on x86. Tested-by: Christian Kujau Thank you! Christian. > > cheers >

Re: Locking API testsuite output mangled

On Wed, 23 Nov 2016, Michael Ellerman wrote: > That's nothing powerpc specific AFAICS, does this fix it? Hm, so s/printk/pr_cont/ - but not in all places? But yeah, this fixes it for me, at least on x86. Tested-by: Christian Kujau Thank you! Christian. > > cheers > > diff --git

Re: Locking API testsuite output mangled

Christian Kujau writes: > The "Locking API testsuite" output during bootup (with > CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks > mangled, possibly related to the recent printk changes (4bcc595ccd80, > "printk: reinstate KERN_CONT for printing

Re: Locking API testsuite output mangled

Christian Kujau writes: > The "Locking API testsuite" output during bootup (with > CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks > mangled, possibly related to the recent printk changes (4bcc595ccd80, > "printk: reinstate KERN_CONT for printing continuation lines").

Locking API testsuite output mangled

The "Locking API testsuite" output during bootup (with CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks mangled, possibly related to the recent printk changes (4bcc595ccd80, "printk: reinstate KERN_CONT for printing continuation lines"). Before (e.g. with v4.6) it looked like

Locking API testsuite output mangled

The "Locking API testsuite" output during bootup (with CONFIG_DEBUG_LOCKING_API_SELFTESTS=y) on this PowerPC system looks mangled, possibly related to the recent printk changes (4bcc595ccd80, "printk: reinstate KERN_CONT for printing continuation lines"). Before (e.g. with v4.6) it looked like