All of lore.kernel.org
 help / color / mirror / Atom feed
From: divya.indi@oracle.com
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
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 08:29:50 -0700	[thread overview]
Message-ID: <fc8fd0b5-f239-462a-6c22-52b99e56a843@oracle.com> (raw)
In-Reply-To: <20190520112304.62db2c8c@gandalf.local.home>



On 05/20/2019 08:23 AM, Steven Rostedt wrote:
> 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!
Working on it. Will send it out soon.

Thanks,
Divya
>
> -- Steve


  reply	other threads:[~2019-05-20 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 18:28 [RFC] Kernel access to Ftrace instances 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
2019-05-20 15:29             ` divya.indi [this message]
  -- 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=fc8fd0b5-f239-462a-6c22-52b99e56a843@oracle.com \
    --to=divya.indi@oracle.com \
    --cc=joe.jin@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.