Andrew Morton wrote: >>> printk is a special case, I think. It's the primary logging/debugging >>> method which can't fail and as it's mostly interpreted by human beings >>> (and developers in problematic cases), it has different maneuvering room >>> on errors - ie. it's far better to print messages w/o header or proper >>> log level than failing to print, which is quite different requirements >>> from other components. >> Andrew, any more comments or suggestions on how to proceed on this? > > Nope. > >> One >> way or the other, I think this is a problem worth solving. > > There are a lot of such problems ;) So, I guess it's NACK w/o suggested alternatives, right? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
