From: Steven Rostedt <rostedt@goodmis.org>
To: Wei Yang <richard.weiyang@linux.alibaba.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Patch v2 0/4] tracing: trivial cleanup
Date: Mon, 14 Sep 2020 18:55:28 -0400 [thread overview]
Message-ID: <20200914185528.77d36e9d@gandalf.local.home> (raw)
In-Reply-To: <20200828034257.GA8994@L-31X9LVDL-1304.local>
On Fri, 28 Aug 2020 11:42:57 +0800
Wei Yang <richard.weiyang@linux.alibaba.com> wrote:
> Steven,
>
> Would you like to pick this up?
>
Hmm, patch 1 and 2 have been accepted (different subjects though):
746cf3459f11859 ("tracing: Simplify defining of the next event id")
36b8aacf2a483ba ("tracing: Save one trace_event->type by using __TRACE_LAST_TYPE")
I'm not sure why I didn't pick up patches 3 and 4. I'm looking into that
now.
-- Steve
> On Sun, Jul 12, 2020 at 09:10:32AM +0800, Wei Yang wrote:
> >Some trivial cleanup for tracing.
> >
> >v2:
> > * drop patch 1
> > * merge patch 4 & 5
> > * introduce a new patch change the return value of tracing_init_dentry()
> >
> >Wei Yang (4):
> > tracing: simplify the logic by defining next to be "lasst + 1"
> > tracing: save one trace_event->type by using __TRACE_LAST_TYPE
> > tracing: toplevel d_entry already initialized
> > tracing: make tracing_init_dentry() returns an integer instead of a
> > d_entry pointer
> >
> > kernel/trace/trace.c | 36 ++++++++++++++--------------
> > kernel/trace/trace.h | 2 +-
> > kernel/trace/trace_dynevent.c | 8 +++----
> > kernel/trace/trace_events.c | 9 ++-----
> > kernel/trace/trace_events_synth.c | 9 +++----
> > kernel/trace/trace_functions_graph.c | 8 +++----
> > kernel/trace/trace_hwlat.c | 8 +++----
> > kernel/trace/trace_kprobe.c | 10 ++++----
> > kernel/trace/trace_output.c | 14 +++++------
> > kernel/trace/trace_printk.c | 8 +++----
> > kernel/trace/trace_stack.c | 12 +++++-----
> > kernel/trace/trace_stat.c | 8 +++----
> > kernel/trace/trace_uprobe.c | 9 ++++---
> > 13 files changed, 66 insertions(+), 75 deletions(-)
> >
> >--
> >2.20.1 (Apple Git-117)
>
next prev parent reply other threads:[~2020-09-14 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 1:10 Wei Yang
2020-07-12 1:10 ` [Patch v2 1/4] tracing: simplify the logic by defining next to be "lasst + 1" Wei Yang
2020-07-12 1:10 ` [Patch v2 2/4] tracing: save one trace_event->type by using __TRACE_LAST_TYPE Wei Yang
2020-07-12 1:10 ` [Patch v2 3/4] tracing: toplevel d_entry already initialized Wei Yang
2020-07-12 1:10 ` [Patch v2 4/4] tracing: make tracing_init_dentry() returns an integer instead of a d_entry pointer Wei Yang
2020-08-28 3:42 ` [Patch v2 0/4] tracing: trivial cleanup Wei Yang
2020-09-14 22:55 ` Steven Rostedt [this message]
2020-09-15 1:32 ` Wei Yang
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=20200914185528.77d36e9d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard.weiyang@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®