From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: Fixes to synthetic events
Date: Tue, 30 Oct 2018 09:13:32 -0400 [thread overview]
Message-ID: <20181030131332.141023797@goodmis.org> (raw)
Linus,
This is not my 4.20 pull request (that will be coming shortly). This
is just some last minute fixes that Masami sent me that I finally got
around to test.
Masami had a couple more fixes to the synthetic events. One was a proper
error return value, and the other is for the self tests.
Please pull the latest trace-v4.19-rc8-3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.19-rc8-3
Tag SHA1: 11638fdbcb30c761886e38a7efb561d6ca11272a
Head SHA1: 0d0352d8b3d6d7ca9a710b40e194cbbaeb841c88
Masami Hiramatsu (2):
tracing: Return -ENOENT if there is no target synthetic event
selftests/ftrace: Fix synthetic event test to delete event correctly
----
kernel/trace/trace_events_hist.c | 4 +++-
.../inter-event/trigger-synthetic-event-createremove.tc | 12 ++++++------
2 files changed, 9 insertions(+), 7 deletions(-)
next reply other threads:[~2018-10-30 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 13:13 Steven Rostedt [this message]
2018-10-30 13:13 ` [PATCH 1/2] tracing: Return -ENOENT if there is no target synthetic event Steven Rostedt
2018-10-30 13:13 ` [PATCH 2/2] selftests/ftrace: Fix synthetic event test to delete event correctly Steven Rostedt
2018-10-30 16:48 ` [PATCH 0/2] [GIT PULL] tracing: Fixes to synthetic events Linus Torvalds
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=20181030131332.141023797@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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).