From: "H. Peter Anvin" <hpa@zytor.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@codemonkey.org.uk>
Subject: Re: [PATCH] Very Trivial - make "After * identify, caps:" messages line up
Date: Tue, 15 Jun 2004 14:45:27 -0700 [thread overview]
Message-ID: <40CF6DF7.8070304@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0406152310390.9908@jjulnx.backbone.dif.dk>
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
>
> /Very/ minor, trivial thing, yes, but those messages have been annoying my
> eyes for a while now so I desided to make them line up - so, here's the
> patch that does that (not sure if a signed-off-by line is needed even for
> trivial stuff like this, but I assume it should go with everything, so...)
> Patch is against 2.6.7-rc3-mm2
>
I think that's what the spaces after CPU: was for... apparently that's gotten
forgotten somehow. Sigh. Please put the extra spaces all in one place.
-hpa
next prev parent reply other threads:[~2004-06-15 21:45 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
2004-06-15 21:44 ` Jesper Juhl
2004-06-15 21:45 ` H. Peter Anvin [this message]
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=40CF6DF7.8070304@zytor.com \
--to=hpa@zytor.com \
--cc=davej@codemonkey.org.uk \
--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.