From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: srostedt@redhat.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: Make output nicely spaced for up to 999 cpus
Date: Fri, 25 Jul 2008 18:11:24 -0400 [thread overview]
Message-ID: <20080725221124.GA837@goodmis.org> (raw)
In-Reply-To: <ea127060ce3764c4b714406be0521171b925a847.1216192501.git.michael@ellerman.id.au>
On Wed, Jul 16, 2008 at 05:15:01PM +1000, Michael Ellerman wrote:
>
> Currently some of the ftrace output goes skewiff if you have more
> than 9 cpus, and some if you have more than 99.
>
> Twiddle with the headers and format strings to make up to 999 cpus
> display without causing spacing problems.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
-- Steve
next prev parent reply other threads:[~2008-07-25 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 7:15 [PATCH] ftrace: Make output nicely spaced for up to 999 cpus Michael Ellerman
2008-07-25 22:11 ` Steven Rostedt [this message]
2008-07-31 3:52 ` Michael Ellerman
2008-07-31 4:01 ` Andrew Morton
2008-07-31 4:07 ` Michael Ellerman
2008-07-31 10:49 ` Steven Rostedt
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=20080725221124.GA837@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=srostedt@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox