Actually it already does, to cover the case where an interrupt handler calls
printk while process-context code is performing a printk.
The nested printk will squirt the message into the log buffer and the
"outer" code will display it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/