public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Steven Rostedt <rostedt@goodmis.org>
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: Thu, 31 Jul 2008 13:52:19 +1000	[thread overview]
Message-ID: <1217476339.1487.24.camel@localhost> (raw)
In-Reply-To: <20080725221124.GA837@goodmis.org>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

On Fri, 2008-07-25 at 18:11 -0400, Steven Rostedt wrote:
> 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>

Hi Steven,

Is there an ftrace tree I should send this to? Or should I ask Andrew to
throw it in -mm ?

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-07-31  3:52 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
2008-07-31  3:52   ` Michael Ellerman [this message]
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=1217476339.1487.24.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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