From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/3] tracing: A few trace event triggers fixes
Date: Sat, 21 Dec 2013 16:43:59 -0600 [thread overview]
Message-ID: <cover.1387662969.git.tom.zanussi@linux.intel.com> (raw)
This patchset fixes a few sparse warnings and build problems seen
under certain configurations, as uncovered by the kbuild test robot.
Applies to linux-trace.git ftrace/core.
The following changes since commit 611e9015501ab9597d6a43253813d4efd90936de:
tracing: Add documentation for trace event triggers (2013-12-20 23:24:20 -0500)
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/event-triggers-ftrace-core-kbuild-robot-fixes
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/event-triggers-ftrace-core-kbuild-robot-fixes
Tom Zanussi (3):
tracing: Move tracing_alloc_snapshot() declaration to tracing.h
tracing: Add and use event_trigger_lseek()
tracing: Add rcu annotation for event_trigger_data.filter
include/linux/kernel.h | 2 --
kernel/trace/trace.h | 3 ++-
kernel/trace/trace_events_trigger.c | 15 ++++++++++++++-
3 files changed, 16 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-12-21 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 22:43 Tom Zanussi [this message]
2013-12-21 22:44 ` [PATCH 1/3] tracing: Move tracing_alloc_snapshot() declaration to tracing.h Tom Zanussi
2013-12-22 2:59 ` Steven Rostedt
2013-12-21 22:44 ` [PATCH 2/3] tracing: Add and use event_trigger_lseek() Tom Zanussi
2013-12-21 22:44 ` [PATCH 3/3] tracing: Add rcu annotation for event_trigger_data.filter Tom Zanussi
2013-12-21 22:53 ` [PATCH 0/3] tracing: A few trace event triggers fixes 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=cover.1387662969.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.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.