Andrew Morton <[email protected]> wrote: > Did you consider doing this within no_printk()? That would break code > which is relying on side-effects in the evaluation of a printk arg but > that's pretty weird and I bet there isn't (and won't be) such code.
The reasons that no_printk() is like it is are (1) so that the side-effects stay intact and (2) you still get format warnings. If someone prints a device register, for example, it *must* work the same whether or not you use printk() or no_printk(). Of course, printing a device register like this is probably not a good idea... David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
