Re: [PATCH] Very Trivial - make "After * identify, caps:" messages line up

[Dave Jones]

On Tue, Jun 15, 2004 at 11:21:44PM +0200, Jesper Juhl wrote:

 > Visually it's much easier to read/compare messages such as these
 > 
 > Jun 15 19:09:02 dragon kernel: CPU:     After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
 > Jun 15 19:09:02 dragon kernel: CPU:     After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
 > 
 > if the numbers line up like this
 > 
 > Jun 15 19:09:02 dragon kernel: CPU:     After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000
 > Jun 15 19:09:02 dragon kernel: CPU:     After vendor identify,  caps: 0183f9ff c1c7f9ff 00000000 00000000

I think it's pointless whilst the third 'after all inits' printk remains
a) unindented  and b) interrupted by other blurb, but in all honesty,
I don't think it really matters, so I won't object either way if it goes in.

		Dave

-
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/