From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Divya Indi <divya.indi@oracle.com>
Cc: linux-kernel@vger.kernel.org, Joe Jin <joe.jin@oracle.com>
Subject: Re: [PATCH] tracing: Kernel access to Ftrace instances
Date: Mon, 20 May 2019 11:23:04 -0400 [thread overview]
Message-ID: <20190520112304.62db2c8c@gandalf.local.home> (raw)
In-Reply-To: <F331FDC8-9E63-4042-A933-BDC197C9A031@goodmis.org>
On Wed, 15 May 2019 20:24:43 -0700
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> >It seems your's already in Steve's ftrace/core branch, so I think you
> >can make
> >additional patch to fix it. Steve, is that OK?
> >
>
> Yes. In fact I already sent a pull request to Linus. Please send a patch on top of my ftrace/core branch.
>
And now it is in mainline (v5.2-rc1). Please send a patch with a sample
module (as Masami requested). Also, that function not only needs to be
changed to not being static, you need to add it to a header
(include/linux/trace_events.h?)
Thanks!
-- Steve
next prev parent reply other threads:[~2019-05-20 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 18:28 [RFC] " Divya Indi
2019-03-20 18:28 ` [PATCH] tracing: " Divya Indi
2019-03-27 16:29 ` Steven Rostedt
2019-05-16 0:09 ` Masami Hiramatsu
2019-05-16 1:51 ` Divya Indi
2019-05-16 3:05 ` Masami Hiramatsu
2019-05-16 3:24 ` Steven Rostedt
2019-05-20 15:23 ` Steven Rostedt [this message]
2019-05-20 15:29 ` divya.indi
-- strict thread matches above, loose matches on Subject: below --
2019-03-15 23:35 [RFC] " Divya Indi
2019-03-15 23:35 ` [PATCH] tracing: Kernel access to ftrace instances Divya Indi
2019-03-19 20:16 ` Steven Rostedt
2019-03-20 18:20 ` divya.indi
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=20190520112304.62db2c8c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=divya.indi@oracle.com \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.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
all inboxes | Powered by JetHome®