From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] [GIT PULL] tracing: A few small fixes to synthetic events
Date: Fri, 19 Oct 2018 21:29:58 -0400 [thread overview]
Message-ID: <20181020012958.223064271@goodmis.org> (raw)
Linus (aka Greg),
Masami found some issues with the creation of synthetic events.
The first two patches fix handling of unsigned type, and handling
of a space before an ending semi-colon.
The third patch adds a selftest to test the processing of synthetic events.
Please pull the latest trace-v4.19-rc8-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.19-rc8-2
Tag SHA1: e97b692b87a195b6f33386989bb7fc7341e27288
Head SHA1: ba0e41ca81b935b958006c7120466e2217357827
Masami Hiramatsu (3):
tracing: Fix synthetic event to accept unsigned modifier
tracing: Fix synthetic event to allow semicolon at end
selftests: ftrace: Add synthetic event syntax testcase
----
kernel/trace/trace_events_hist.c | 32 +++++++--
.../inter-event/trigger-synthetic-event-syntax.tc | 80 ++++++++++++++++++++++
2 files changed, 105 insertions(+), 7 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-synthetic-event-syntax.tc
next reply other threads:[~2018-10-20 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 1:29 Steven Rostedt [this message]
2018-10-20 1:29 ` [PATCH 1/3] tracing: Fix synthetic event to accept unsigned modifier Steven Rostedt
2018-10-20 1:30 ` [PATCH 2/3] tracing: Fix synthetic event to allow semicolon at end Steven Rostedt
2018-10-20 1:30 ` [PATCH 3/3] selftests: ftrace: Add synthetic event syntax testcase Steven Rostedt
2018-10-20 7:39 ` [PATCH 0/3] [GIT PULL] tracing: A few small fixes to synthetic events Greg Kroah-Hartman
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=20181020012958.223064271@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.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 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.