From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] [GIT PULL][3.8] tracing: Minor fixes for 3.8
Date: Wed, 02 Jan 2013 17:50:35 -0500 [thread overview]
Message-ID: <20130102225035.140076434@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
Ingo,
As it's still an early -rc, it would be good to get these fixes into
mainline before the next release.
Thanks,
-- Steve
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: f9dd9809c1426ccc7e997201b9b839c96ac810ec
Jovi Zhang (1):
tracing: Verify target file before registering a uprobe event
Steven Rostedt (2):
ftrace: Be first to run code modification on modules
tracing: Fix sparse warning with is_signed_type() macro
----
include/linux/ftrace_event.h | 2 +-
kernel/trace/ftrace.c | 2 +-
kernel/trace/trace_uprobe.c | 6 +++++-
3 files changed, 7 insertions(+), 3 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2013-01-03 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 22:50 Steven Rostedt [this message]
2013-01-02 22:50 ` [PATCH 1/3] ftrace: Be first to run code modification on modules Steven Rostedt
2013-01-02 22:50 ` [PATCH 2/3] tracing: Fix sparse warning with is_signed_type() macro Steven Rostedt
2013-01-02 22:50 ` [PATCH 3/3] tracing: Verify target file before registering a uprobe event Steven Rostedt
2013-01-04 4:30 ` Namhyung Kim
2013-01-07 13:59 ` Steven Rostedt
2013-01-07 15:57 ` Steven Rostedt
2013-01-24 19:37 ` [tip:perf/core] " tip-bot for Jovi Zhang
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=20130102225035.140076434@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox