From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [FIX PATCH v2] selftests: tracing: Fix to unmount tracefs for recovering environment
Date: Wed, 13 Sep 2023 12:01:34 +0900 [thread overview]
Message-ID: <20230913120134.ebe446942ad5d3b883c3e9a6@kernel.org> (raw)
In-Reply-To: <49f6d44b-b6e8-bfca-1df7-3ab94684902e@linuxfoundation.org>
On Tue, 12 Sep 2023 09:35:58 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 9/11/23 19:24, Steven Rostedt wrote:
> > On Tue, 12 Sep 2023 10:10:39 +0900
> > "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> >
> >> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >>
> >> Fix to unmount the tracefs if the ftracetest mounted it for recovering
> >> system environment. If the tracefs is already mounted, this does nothing.
> >>
> >> Suggested-by: Mark Brown <broonie@kernel.org>
> >> Link: https://lore.kernel.org/all/29fce076-746c-4650-8358-b4e0fa215cf7@sirena.org.uk/
> >> Fixes: cbd965bde74c ("ftrace/selftests: Return the skip code when tracing directory not configured in kernel")
> >> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >> ---
> >> Changes in v2:
> >> - use -n option explictly for testing the string is non-zero.
> >> ---
> >> tool
> >
> > Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> >
> > -- Steve
>
> Thank you all. Applied to linux-kselftest fixes branch for next rc
>
Thanks Shuah!
> thanks,
> -- Shuah
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-09-13 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 1:10 Masami Hiramatsu (Google)
2023-09-12 1:24 ` Steven Rostedt
2023-09-12 15:35 ` Shuah Khan
2023-09-13 3:01 ` Masami Hiramatsu [this message]
2023-09-12 11:35 ` Mark Brown
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=20230913120134.ebe446942ad5d3b883c3e9a6@kernel.org \
--to=mhiramat@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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®