On Mon, 2009-10-26 at 22:25 +0800, Wu Zhangjin wrote: > Hi, > > On Mon, 2009-10-26 at 10:01 -0400, Steven Rostedt wrote: > [...] > > Some patches touch core tracing code, and some are arch specific. Now > > the question is how do we go. I prefer that we go the path of the > > tracing tree (easier for me to test). > > Just coped with the feedbacks from Frederic Weisbecker. > > I will rebase the whole patches to your git repo(the following one?) and > send them out as the -v6 revision: > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git tip/tracing/core Actually, I always base off of tip itself. Don't use mine. Use this one: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git tracing/core Then we will stay in sync. > > > But every patch that touches MIPS > > arch, needs an Acked-by from the MIPS maintainer. Which I see is Ralf > > (on the Cc of this patch set.) > > > > Looking forward to the feedback from Ralf, Seems he is a little busy. > and also looking forward to the testing result from the other MIPS > developers, so, we can ensure ftrace for MIPS really function! > > Welcome to clone this branch and test it: > > git://dev.lemote.com/rt4ls.git linux-mips/dev/ftrace-upstream I already have your repo as a remote ;-) > > And this document will tell you how to play with it: > Documentation/trace/ftrace.txt Did you add to it? Thanks, -- Steve
