From: Andrew Morton <akpm@linux-foundation.org>
To: michael@ellerman.id.au
Cc: Steven Rostedt <rostedt@goodmis.org>,
srostedt@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: Make output nicely spaced for up to 999 cpus
Date: Wed, 30 Jul 2008 21:01:44 -0700 [thread overview]
Message-ID: <20080730210144.0f4970c9.akpm@linux-foundation.org> (raw)
In-Reply-To: <1217476339.1487.24.camel@localhost>
On Thu, 31 Jul 2008 13:52:19 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> 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>
I switched that to Acked-by:. A Signed-off-by: implies that you
(co)authored the patch or that it went through your hands. That does
not appear to be the case here.
> Hi Steven,
>
> Is there an ftrace tree I should send this to? Or should I ask Andrew to
> throw it in -mm ?
Normally Ingo handles ftrace but he will shortly be offline for a bit,
so I'll suck up whatever Ingoish things happen to cross my desk.
next prev parent reply other threads:[~2008-07-31 4:02 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
2008-07-31 4:01 ` Andrew Morton [this message]
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=20080730210144.0f4970c9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--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