linux-kernel - Re: [PATCH] ftrace: Make output nicely spaced for up to 999 cpus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Jul 2008 21:01:44 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	michael@...erman.id.au
Cc:	Steven Rostedt <rostedt@...dmis.org>, srostedt@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ftrace: Make output nicely spaced for up to 999 cpus

On Thu, 31 Jul 2008 13:52:19 +1000 Michael Ellerman <michael@...erman.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@...erman.id.au>
> > 
> > Signed-off-by: Steven Rostedt <srostedt@...hat.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/