> But that actually argues *more* for moving to a world where that
> (common, but also often-forgotten) final '\n' at the end should be
> de-emphasized. So I don't think it would be at all wrong to expect
> that
>
> printk("Line A");
> printk("Line B");
>
> should print two lines. We very much had that KERN_CONT to encode the
> *exception* to this, for the (not very common) cases where we end up
> listing multiple things on one line.
Of course if people *really* want things on the same line, they usually end
up using sprintf() to save the individual pieces to some buffer and the dump
that out using one printk() call ... because KERN_CONT isn't much help when
some other code comes along and drops its own output in the middle of
what you were trying to pretty print.
-Tony
��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
