linux-kernel - Re: [PATCH 1/2] ftrace, powerpc: replace debug macro with proper pr

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]

Message-ID: <alpine.DEB.1.10.0902060828050.10059@gandalf.stny.rr.com>
Date:	Fri, 6 Feb 2009 08:29:39 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
cc:	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Neuling <mikey@...ling.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 1/2] ftrace, powerpc: replace debug macro with proper
 pr_deug


On Fri, 6 Feb 2009, Benjamin Herrenschmidt wrote:

> On Fri, 2009-02-06 at 01:03 -0500, Steven Rostedt wrote:
> > plain text document attachment
> > (0001-ftrace-powerpc-replace-debug-macro-with-proper-pr_.patch)
> > From: Steven Rostedt <srostedt@...hat.com>
> > 
> > Impact: cleanup
> > 
> > The PowerPC ftrace code uses a hacked up DEBUGP macro for prints.
> > This patch converts it to the standard pr_debug.
> >
> > Signed-off-by: Steven Rostedt <srostedt@...hat.com>
> 
> Acked-by: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> ---
> 
> Want me to go through powerpc tree or you'll merge via Ingo ?

These two changes are powerpc specific. I think it may get more testing 
going through the powerpc tree than through tip.

-- Steve

--
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/