From: Steven Rostedt <rostedt@goodmis.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Juerg Haefliger <juerg.haefliger@canonical.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH selftests 0/2] Add checkbashisms meta-testcase
Date: Thu, 23 May 2019 22:31:14 -0400 [thread overview]
Message-ID: <20190523223114.4feb6239@oasis.local.home> (raw)
In-Reply-To: <20190323192746.59739e5e9ea0445791ac14ed@kernel.org>
Shuah,
Want to take this or would you want me to?
-- Steve
On Sat, 23 Mar 2019 19:27:46 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hi Shuah,
>
> Could you pick this to your tree? I think this can prevent further
> simillar errors before release...
>
> Thank you,
>
> On Fri, 22 Feb 2019 10:26:27 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Hi,
> >
> > Here are patches for making sure the ftracetest testcases
> > are checkbashisms clean.
> >
> > This actually needs a patch from Juerg, "selftests/ftrace:
> > Make the coloring POSIX compliant" to complete the work.
> >
> > http://lkml.kernel.org/r/20190220161333.28109-1-juergh@canonical.com
> > (Note that this is still under development)
> >
> > So as Juerg pointed, recently ftracetest becomes not POSIX
> > compliant, and such kind of issues happened repeatedly.
> > To avoid those anymore, I decided to introduce a testcase
> > which runs checkbasisms on ftracetest and its testcases.
> > I think this can help us to find out whether it was
> > written in a way out of POSIX.
> >
> > Thank you,
> >
> > ---
> >
> > Masami Hiramatsu (2):
> > selftests/ftrace: Make a script checkbashisms clean
> > selftests/ftrace: Add checkbashisms meta-testcase
> >
> >
> > tools/testing/selftests/ftrace/ftracetest | 1 +
> > .../ftrace/test.d/kprobe/kprobe_ftrace.tc | 2 +-
> > .../selftests/ftrace/test.d/selftest/bashisms.tc | 21 ++++++++++++++++++++
> > 3 files changed, 23 insertions(+), 1 deletion(-)
> > create mode 100644 tools/testing/selftests/ftrace/test.d/selftest/bashisms.tc
> >
> > --
> > Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
>
>
next prev parent reply other threads:[~2019-05-24 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 1:26 [PATCH selftests 0/2] Add checkbashisms meta-testcase Masami Hiramatsu
2019-02-22 1:26 ` [PATCH selftests 1/2] selftests/ftrace: Make a script checkbashisms clean Masami Hiramatsu
2019-02-22 1:27 ` [PATCH selftests 2/2] selftests/ftrace: Add checkbashisms meta-testcase Masami Hiramatsu
2019-03-23 10:27 ` [PATCH selftests 0/2] " Masami Hiramatsu
2019-05-24 2:31 ` Steven Rostedt [this message]
2019-05-24 3:02 ` shuah
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=20190523223114.4feb6239@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).