From: Dave Jones <davej@redhat.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: [PATCH] Very Trivial - make "After * identify, caps:" messages line up
Date: Tue, 15 Jun 2004 22:33:30 +0100 [thread overview]
Message-ID: <20040615213330.GA6471@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0406152310390.9908@jjulnx.backbone.dif.dk>
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
next prev parent reply other threads:[~2004-06-15 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 21:21 [PATCH] Very Trivial - make "After * identify, caps:" messages line up Jesper Juhl
2004-06-15 21:33 ` Dave Jones [this message]
2004-06-15 21:44 ` Jesper Juhl
2004-06-15 21:45 ` H. Peter Anvin
2004-06-15 21:51 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040615213330.GA6471@redhat.com \
--to=davej@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.