Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
On Sat, Mar 02, 2013 at 10:12:40PM -0800, Christopher Li wrote: > On Sat, Mar 2, 2013 at 5:23 AM, Fengguang Wu wrote: > > That's it! Verified with > > > > make C=1 kernel/trace/trace_functions.o > > You can use C=2 to run sparse without recompile the obj file. Got it, thanks!

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Christopher Li
On Sat, Mar 2, 2013 at 5:23 AM, Fengguang Wu wrote: > That's it! Verified with > > make C=1 kernel/trace/trace_functions.o You can use C=2 to run sparse without recompile the obj file. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
On Sat, Mar 02, 2013 at 08:15:22AM -0500, Steven Rostedt wrote: > On Sat, 2013-03-02 at 08:12 -0500, Steven Rostedt wrote: > > > Hmm, actually it seems to be complaining everywhere but in trace.c which > > is where the per_cpu was allocated. Do I need to annotate the trace.h > > header to specify

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
// add CC to Christopher. On Sat, Mar 02, 2013 at 08:12:52AM -0500, Steven Rostedt wrote: > On Sat, 2013-03-02 at 15:41 +0800, kbuild test robot wrote: > > tree: > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git > > tip/perf/core > > head:

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Steven Rostedt
On Sat, 2013-03-02 at 08:12 -0500, Steven Rostedt wrote: > Hmm, actually it seems to be complaining everywhere but in trace.c which > is where the per_cpu was allocated. Do I need to annotate the trace.h > header to specify (at least to sparse) that the pointer is allocated per > cpu? I guess I

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Steven Rostedt
On Sat, 2013-03-02 at 15:41 +0800, kbuild test robot wrote: > tree: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git > tip/perf/core > head: f44f8638e47c89fa5c612a18f324ba6222b69597 > commit: 50b85fe13be0878f13eecd36d1219828ba73316d [5/15] tracing: Replace the > static

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Christopher Li
On Sat, Mar 2, 2013 at 5:23 AM, Fengguang Wu fengguang...@intel.com wrote: That's it! Verified with make C=1 kernel/trace/trace_functions.o You can use C=2 to run sparse without recompile the obj file. Chris -- To unsubscribe from this list: send the line unsubscribe linux-kernel in

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
On Sat, Mar 02, 2013 at 10:12:40PM -0800, Christopher Li wrote: On Sat, Mar 2, 2013 at 5:23 AM, Fengguang Wu fengguang...@intel.com wrote: That's it! Verified with make C=1 kernel/trace/trace_functions.o You can use C=2 to run sparse without recompile the obj file. Got it,

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Steven Rostedt
On Sat, 2013-03-02 at 15:41 +0800, kbuild test robot wrote: tree: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git tip/perf/core head: f44f8638e47c89fa5c612a18f324ba6222b69597 commit: 50b85fe13be0878f13eecd36d1219828ba73316d [5/15] tracing: Replace the static global

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Steven Rostedt
On Sat, 2013-03-02 at 08:12 -0500, Steven Rostedt wrote: Hmm, actually it seems to be complaining everywhere but in trace.c which is where the per_cpu was allocated. Do I need to annotate the trace.h header to specify (at least to sparse) that the pointer is allocated per cpu? I guess I need

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
// add CC to Christopher. On Sat, Mar 02, 2013 at 08:12:52AM -0500, Steven Rostedt wrote: On Sat, 2013-03-02 at 15:41 +0800, kbuild test robot wrote: tree: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git tip/perf/core head:

Re: [trace:tip/perf/core 5/15] kernel/trace/trace_functions.c:79:16: sparse: incorrect type in initializer (different address spaces)

2013-03-02 Thread Fengguang Wu
On Sat, Mar 02, 2013 at 08:15:22AM -0500, Steven Rostedt wrote: On Sat, 2013-03-02 at 08:12 -0500, Steven Rostedt wrote: Hmm, actually it seems to be complaining everywhere but in trace.c which is where the per_cpu was allocated. Do I need to annotate the trace.h header to specify (at