From: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jovi Zhang <bookjovi@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2] tracing: Expose event tracing infrastructure
Date: Sat, 23 Mar 2013 18:42:25 +0800 [thread overview]
Message-ID: <514D8711.8020303@huawei.com> (raw)
In-Reply-To: <1363351889.25967.51.camel@gandalf.local.home>
On 2013/3/15 20:51, Steven Rostedt wrote:
> On Fri, 2013-03-15 at 20:31 +0800, Jovi Zhang wrote:
>
>> Hi steven,
>>
>> Would you please give some comments? patch works normally on my box.
>
> Yeah, I planned on it today ;-) Actually, I've been a busy beaver
> lately. The last couple of weeks I have:
>
> 32 files changed, 5239 insertions(+), 1805 deletions(-)
>
> (Although some of that work started back last August)
>
> I still have to finish backporting the patches I said I would take from
> you from earlier this week.
>
> Anyway, a quick scan of the patch looks fine, and I don't see any major
> issues with it. The only problem is that the changes I've made have
> touched this code a bit and your patch won't apply, with my new work.
Steven, I just saw you have sent a pull request to Ingo with a large update on tracing code,
and bring a little conflicts with this "Expose event tracing infrastructure" patch,
like ftrace_event_file introduced in ftrace_raw_event_<call>.
Do I need to resend this patch based on your new work?(and testing) to make you can merge this patch easily.
Thanks.
>
> I'm just about finished, the final tests I'm doing on my code are
> looking good and I'm hoping to push my final version to linux-next
> today. If you want to have a head start, you can look at the current
> code (no guarantee that it wont rebase), at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace/tip/perf/core-5
>
> -- Steve
>
>
>
>
next prev parent reply other threads:[~2013-03-23 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 10:41 [PATCH v2] tracing: Expose event tracing infrastructure zhangwei(Jovi)
2013-03-15 12:31 ` Jovi Zhang
2013-03-15 12:51 ` Steven Rostedt
2013-03-23 10:42 ` zhangwei(Jovi) [this message]
2013-03-23 15:14 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514D8711.8020303@huawei.com \
--to=jovi.zhangwei@huawei.com \
--cc=bookjovi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox