[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20B470EF-C8A2-4CC3-A266-60FF51AB5A94@163.com>
Date: Fri, 17 Jul 2015 22:43:09 +0800
From: pi3orama <pi3orama@....com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Wangnan (F)" <wangnan0@...wei.com>, He Kuang <hekuang@...wei.com>,
"<ast@...mgrid.com>" <ast@...mgrid.com>,
"<masami.hiramatsu.pt@...achi.com>" <masami.hiramatsu.pt@...achi.com>,
"<acme@...nel.org>" <acme@...nel.org>,
"<a.p.zijlstra@...llo.nl>" <a.p.zijlstra@...llo.nl>,
"<mingo@...hat.com>" <mingo@...hat.com>,
"<namhyung@...nel.org>" <namhyung@...nel.org>,
"<jolsa@...nel.org>" <jolsa@...nel.org>,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v5 2/3] tools lib traceevent: Add function to get dynamic arrays length
发自我的 iPhone
> 在 2015年7月17日,下午10:36,Steven Rostedt <rostedt@...dmis.org> 写道:
>
>
> Is this dependent on patch 1? Because I'm not sure that's going to be
> the ending fix.
>
>
> On Fri, 17 Jul 2015 11:36:54 +0800
> "Wangnan (F)" <wangnan0@...wei.com> wrote:
>
>> Here is a small problem in this patch that, it only updates
>> trace-event-python.c, leaves
>> trace-event-perf.c unchanged. If CONFIG_LIBPERL is on, a compiling error
>> will raise.
>>
>> I fixed this in my own git repository.
>>
>> Steven, could you please cherry-pick this one instead?
>>
>> https://github.com/WangNan0/linux/commit/951d78339e8c7819e9a1a9faeaf15e2c0b1aaa10
>
> Please repost a proper patch to the mailing list.
>
> Also, Arnaldo is the one that pulls in changes to the
> tools/lib/traceevent code. But I would need to ack it first.
>
I'll wait for your conclusion on patch 1, and let He Kuang to repost it if this patch is still required.
Thanks.
> -- Steve
>
>>
>> Note that the author field of it is still He Kuang.
>>
>> Thank you.
>>
>>> /* we should warn... */
>>> return;
>>> }
>
--
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/
Powered by blists - more mailing lists