All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [for-next][PATCH 0/4] tracing: More updates for 3.15
Date: Wed, 19 Mar 2014 22:58:31 -0400	[thread overview]
Message-ID: <20140320025831.285817697@goodmis.org> (raw)

Minor changes, but this includes updates from Mathieu Desnoyers for
fixing the documentation of the way the current code works in my next
repo. He's currently working on other ways to handle the changes, but
until that is ready, this will have to do.

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: cb1deb5fc1fded22401c0e9ca6bda056a7f1b553


Jiri Slaby (1)
      ftrace: Fix compilation warning about control_ops_free

Mathieu Desnoyers (2)
      tracepoints: API doc update to data argument
      tracepoints: API doc update to tracepoint_probe_register() return value

Sasha Levin (1)
      ftrace: Constify ftrace_text_reserved

----
 include/linux/ftrace.h |    4 ++--
 kernel/trace/ftrace.c  |   12 ++++++------
 kernel/tracepoint.c    |   16 +++++++++++++++-
 3 files changed, 23 insertions(+), 9 deletions(-)

             reply	other threads:[~2014-03-20  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  2:58 Steven Rostedt [this message]
2014-03-20  2:58 ` [for-next][PATCH 1/4] ftrace: Fix compilation warning about control_ops_free Steven Rostedt
2014-03-20  2:58 ` [for-next][PATCH 2/4] tracepoints: API doc update to data argument Steven Rostedt
2014-03-20  2:58 ` [for-next][PATCH 3/4] tracepoints: API doc update to tracepoint_probe_register() return value Steven Rostedt
2014-03-20  2:58 ` [for-next][PATCH 4/4] ftrace: Constify ftrace_text_reserved 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=20140320025831.285817697@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@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 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.