Hi, On (08/29/17 22:24), Pavel Machek wrote: > > > In 4.13-rc, printk("foo"); printk("bar"); seems to produce > > > foo\nbar. That's... quite surprising/unwelcome. What is going on > > > there? Are timestamps responsible? > > > > No. > > > > It's actively trying to treach you not to do shit. > > > > If you want to continue a line, you NEED to use KERN_CONT. > > > > That has always been true. It hasn't always been enforced, though. > > Dumping hex buffer for debugging should not be a rocket science. You > are welcome not add checkpatch rules to prevent such code from being > merged...
well... just a note, I personally developed a new habit - use pr_err/pr_cont/etc macros instead of explicit printk(KERN_FOO "..."). may be this can work for you. and we _probably_ need to advertise pr_foo() more. -ss