From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUGFIX PATCH 3/3] selftests/ftrace: Do not to use absolute debugfs path
Date: Sun, 24 Nov 2019 16:42:12 -0500 [thread overview]
Message-ID: <20191124164212.50029da6@oasis.local.home> (raw)
In-Reply-To: <157457135713.25666.16389902435164296254.stgit@devnote2>
On Sun, 24 Nov 2019 13:55:57 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Use relative path to trigger file instead of absolute debugfs path,
> because if the user uses tracefs instead of debugfs, it can be
> mounted at /sys/kernel/tracing.
> Anyway, since the ftracetest is designed to be run at the tracing
> directory, user doesn't need to use absolute path.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
>
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
prev parent reply other threads:[~2019-11-24 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 4:55 [BUGFIX PATCH 0/3] selftests/ftrace: Fix ftracetest testcases for non-function tracer case Masami Hiramatsu
2019-11-24 4:55 ` [BUGFIX PATCH 1/3] selftests/ftrace: Fix to check the existence of set_ftrace_filter Masami Hiramatsu
2019-11-24 21:35 ` Steven Rostedt
2019-11-24 23:34 ` Masami Hiramatsu
2019-11-24 4:55 ` [BUGFIX PATCH 2/3] selftests/ftrace: Fix ftrace test cases to check unsupported Masami Hiramatsu
2019-11-24 21:39 ` Steven Rostedt
2019-11-24 23:36 ` Masami Hiramatsu
2019-11-24 4:55 ` [BUGFIX PATCH 3/3] selftests/ftrace: Do not to use absolute debugfs path Masami Hiramatsu
2019-11-24 21:42 ` Steven Rostedt [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=20191124164212.50029da6@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®