Rene Herman wrote:
Okay. I would by the way not be against turning the timestamping off by
default and turning it _on_ with a "timestamps" or "logtime" or whatever option. The information is sometimes handy for seeing the (clustering of) event times so I've been compiling it in for a while on
some boxes but in the majority case for me it's noise taking up printk
real estate...
But CONFIG_PRINTK_TIME is what controls its "default" (build-time) value.
I.e., users can control that.
I would be OK with removing that config option and only being able to
enable it, but I doubt that this would have much support. ;)