linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Zanussi <tzanussi@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: artem.bityutskiy@linux.intel.com, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH v4 06/12] tracing: Change trace_boot to use synth_event interface
Date: Fri, 31 Jan 2020 12:01:18 -0600	[thread overview]
Message-ID: <1580493678.24839.6.camel@gmail.com> (raw)
In-Reply-To: <20200131130020.51d04203@gandalf.local.home>

On Fri, 2020-01-31 at 13:00 -0500, Steven Rostedt wrote:
> On Fri, 31 Jan 2020 12:55:39 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > On Fri, 31 Jan 2020 11:49:01 -0600
> > Tom Zanussi <tzanussi@gmail.com> wrote:
> > 
> > > Hi Steve,
> > > 
> > > It looks like you missed this patch when you pulled the other
> > > ones into
> > >  for-next.
> > >   
> > 
> > Ah, you're right! And my INBOX patchwork is informing me of it too
> > (I
> > have it read my email, and when I post the 'for-next' patches, it
> > switches the status from "new" to "Under review", and this one is
> > still
> > "new").
> > 
> > Thanks for letting me know. I'll apply it now.
> 
> My latest has been pushed to ftrace/core.

Thanks!

Tom

> 
> -- Steve

  reply	other threads:[~2020-01-31 18:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 18:59 [PATCH v4 00/12] tracing: Add support for in-kernel dynamic event API Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 01/12] tracing: Add trace_array_find/_get() to find instance trace arrays Tom Zanussi
2020-01-29 21:14   ` Steven Rostedt
2020-01-29 18:59 ` [PATCH v4 02/12] tracing: Add trace_get/put_event_file() Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 03/12] tracing: Add synth_event_delete() Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 04/12] tracing: Add dynamic event command creation interface Tom Zanussi
2020-01-30  2:40   ` Masami Hiramatsu
2020-01-30  2:58     ` Steven Rostedt
2020-01-29 18:59 ` [PATCH v4 05/12] tracing: Add synthetic event command generation functions Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 06/12] tracing: Change trace_boot to use synth_event interface Tom Zanussi
2020-01-31 17:49   ` Tom Zanussi
2020-01-31 17:55     ` Steven Rostedt
2020-01-31 18:00       ` Steven Rostedt
2020-01-31 18:01         ` Tom Zanussi [this message]
2020-01-29 18:59 ` [PATCH v4 07/12] tracing: Add synth_event_trace() and related functions Tom Zanussi
2020-01-29 21:09   ` Steven Rostedt
2020-01-29 22:58     ` Tom Zanussi
2020-01-30  3:01       ` Steven Rostedt
2020-01-29 18:59 ` [PATCH v4 08/12] tracing: Add synth event generation test module Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 09/12] tracing: Add kprobe event command generation functions Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 10/12] tracing: Change trace_boot to use kprobe_event interface Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 11/12] tracing: Add kprobe event command generation test module Tom Zanussi
2020-01-29 18:59 ` [PATCH v4 12/12] tracing: Documentation for in-kernel synthetic event API Tom Zanussi

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=1580493678.24839.6.camel@gmail.com \
    --to=tzanussi@gmail.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).