On Thu, 22 Aug 2013, Andrew Morton wrote: > Years of hard experience have taught me: don't muck with printk. It > needs to be robust, simple and to have minimum dependency on both the > calling environment and on correctly functioning kernel components. > printk and NMI are the harshest environments we have to deal with.
NMI is harsh due to its design. printk() is harsh because of the way we have implemented it. So we'd better work on fixing it, methinks. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/