[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYtLQN_dMXUE0zVbWmtYjpu16hbShMb+mxQh3tiedwrXuQ@mail.gmail.com>
Date: Thu, 1 Oct 2020 10:39:50 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Kees Cook <keescook@...omium.org>
Cc: Shuah Khan <shuah@...nel.org>, Hangbin Liu <liuhangbin@...il.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
Tim.Bird@...y.com, lkft-triage@...ts.linaro.org,
Anders Roxell <anders.roxell@...aro.org>,
Justin Cook <justin.cook@...aro.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH v2 2/3] selftests/run_kselftest.sh: Make each test
individually selectable
On Tue, 29 Sep 2020 at 01:56, Kees Cook <keescook@...omium.org> wrote:
>
> Currently with run_kselftest.sh there is no way to choose which test
> we could run. All the tests listed in kselftest-list.txt are all run
> every time. This patch enhanced the run_kselftest.sh to make the test
> collections (or tests) individually selectable. e.g.:
>
> $ ./run_kselftest.sh -c seccomp -t timers:posix_timers -t timers:nanosleep
>
> Additionally adds a way to list all known tests with "-l", usage
> with "-h", and perform a dry run without running tests with "-n".
>
> Co-developed-by: Hangbin Liu <liuhangbin@...il.com>
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
> Signed-off-by: Kees Cook <keescook@...omium.org>
Tested-by: Naresh Kamboju <naresh.kamboju@...aro.org>
- Naresh
Powered by blists - more mailing lists