Re: [PATCH] printk: Ensure oops printing if console is locked

[Greg Kroah-Hartman]

On Wed, Jun 13, 2012 at 11:14:12AM +0200, Aurelien Gerault wrote:
> From: Aurelien Gerault <aurelien.gerault-nonst@xxxxxxxxxxxxxx>
> 
> Ensuring that oops & panic messages/backtraces will be printed
> in console, even when the console is locked.
> 
> If console is locked by someone else but an oops is ongoing, force
> unlocking / re-locking to display the oops.
> 
> Signed-off-by: Aurelien Gerault <aurelien.gerault-nonst@xxxxxxxxxxxxxx>
> ST-Ericsson Linux next: NA
> ST-Ericsson ID: 436456
> ST-Ericsson FOSS-OUT ID: Trivial

What are those fields for?

> Change-Id: I9f571492fefc32291ecd0cc62f0ad7031cab7c6d

What is this for?

Please clean up the patch before sending it out publicly, we can't take
stuff like this...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/