Re: linux-next: build failure after merge of the ftrace tree

[Steven Rostedt]

On Sat, 2013-03-02 at 14:42 +1100, Stephen Rothwell wrote:
> Hi Steve,
> 
> On Fri, 01 Mar 2013 21:45:18 -0500 Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> >
> > On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> > > 
> > > After merging the ftrace tree, today's linux-next build (x86_64
> > > allmodconfig) failed like this:
> > > 
> > > kernel/trace/trace_kdb.c: In function 'ftrace_dump_buf':
> > > kernel/trace/trace_kdb.c:29:33: error: invalid type argument of '->' (have 'struct trace_array_cpu')
> > > kernel/trace/trace_kdb.c:86:33: error: invalid type argument of '->' (have 'struct trace_array_cpu')
> > > 
> > > Caused by commit eaac1836c10e ("tracing: Replace the static global
> > > per_cpu arrays with allocated per_cpu").
> > > 
> > > I have used the ftrace tree from next-20130228 for today.
> > 
> > I rebased, and it should all be good now. I also fixed breakage to the
> > new snapshot feature. Here's my diff:
> 
> Of course, I wonder if this is intended for the current merge window
> (since it turned up in linux-next so late).  If not, then please don;t
> put it in your -next included branch until after -rc1 is released.  If
> you are aiming for this merge window, then good luck!  ;-)
> 

Oh crap, sorry. Quite the contrary. I should have waited for -rc1 as
this is intended for v3.10.

I made some major changes and wanted testing on it as soon as possible.
I've done tons of testing on my own but I wanted a broader audience. Do
you want me to pull my tree and reset it to what is only for 3.9?

All changes I wanted for 3.9 have already made it into Linus's tree.
Everything I've been pushing is destined for 3.10. But as I said. They
are big changes and wanted testing on them early. But it can wait for an
-rc1 window.

-- Steve


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