Re: [PATCH] printk: drop ambiguous LOG_CONT flag

["Jan H. SchÃnherr"]

Am 27.09.2012 17:46, schrieb "Jan H. SchÃnherr":
> If we say "if LOG_CONT is set, this message continues the previous one",
> we can also say "there is no prefix on this message". Then on the other
> hand, we would need a "whatever comes next, it does not continue this
> message"....

Thinking a bit longer about this one.

If really, really everything passes through vprintk_emit()
then we could keep all info about the previous message
there and definitely decide whether the current message continues
the previous one.

Then, we wouldn't need to track the previous flags everywhere.

Do I miss something?

Regards
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/