From: shuah <shuah@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah <shuah@kernel.org>
Subject: Re: [BUGFIX PATCH v4 0/4] selftests/ftrace: Fix ftracetest testcases for non-function tracer case
Date: Tue, 26 Nov 2019 10:37:33 -0700 [thread overview]
Message-ID: <6e05af26-584e-3f03-c63f-b2603a5a9620@kernel.org> (raw)
In-Reply-To: <157475724667.3389.15752644047898709246.stgit@devnote2>
On 11/26/19 1:34 AM, Masami Hiramatsu wrote:
> Hi,
>
> Here is the 4th version of patches to fix some issues which happens on
> the kernel with CONFIG_FUNCTION_TRACER=n or CONFIG_DYNAMIC_FTRACE=n.
>
> In this version I fixed [1/4] to cleanup set_ftrace_notrace (Thanks Steve!)
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (4):
> selftests/ftrace: Fix to check the existence of set_ftrace_filter
> selftests/ftrace: Fix ftrace test cases to check unsupported
> selftests/ftrace: Do not to use absolute debugfs path
> selftests/ftrace: Fix multiple kprobe testcase
>
>
> .../ftrace/test.d/ftrace/func-filter-stacktrace.tc | 2 ++
> .../selftests/ftrace/test.d/ftrace/func_cpumask.tc | 5 +++++
> tools/testing/selftests/ftrace/test.d/functions | 5 ++++-
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 6 +++---
> .../inter-event/trigger-action-hist-xfail.tc | 4 ++--
> .../inter-event/trigger-onchange-action-hist.tc | 2 +-
> .../inter-event/trigger-snapshot-action-hist.tc | 4 ++--
> 7 files changed, 19 insertions(+), 9 deletions(-)
>
> --
> Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
>
Hi Masami and Steve,
Thanks. I will pull these in for 5.5-rc1
-- Shuah
prev parent reply other threads:[~2019-11-26 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 8:34 [BUGFIX PATCH v4 0/4] selftests/ftrace: Fix ftracetest testcases for non-function tracer case Masami Hiramatsu
2019-11-26 8:34 ` [BUGFIX PATCH v4 1/4] selftests/ftrace: Fix to check the existence of set_ftrace_filter Masami Hiramatsu
2019-11-26 17:24 ` Steven Rostedt
2019-11-26 8:34 ` [BUGFIX PATCH v4 2/4] selftests/ftrace: Fix ftrace test cases to check unsupported Masami Hiramatsu
2019-11-26 17:49 ` Steven Rostedt
2019-11-26 23:31 ` Masami Hiramatsu
2019-11-26 23:42 ` [BUGFIX PATCH v4.1 " Masami Hiramatsu
2019-11-26 23:50 ` [BUGFIX PATCH v4 " shuah
2019-11-27 2:15 ` Steven Rostedt
2019-11-26 8:34 ` [BUGFIX PATCH v4 3/4] selftests/ftrace: Do not to use absolute debugfs path Masami Hiramatsu
2019-11-26 8:34 ` [BUGFIX PATCH v4 4/4] selftests/ftrace: Fix multiple kprobe testcase Masami Hiramatsu
2019-11-26 17:37 ` shuah [this message]
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=6e05af26-584e-3f03-c63f-b2603a5a9620@kernel.org \
--to=shuah@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@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 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).