From: David Gow <davidgow@google.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Brendan Higgins <brendanhiggins@google.com>,
John Johansen <john.johansen@canonical.com>,
jmorris@namei.org, serge@hallyn.com,
"Theodore Ts'o" <tytso@mit.edu>,
adilger.kernel@dilger.ca,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
linux-security-module@vger.kernel.org,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v2 2/6] kunit: default KUNIT_* fragments to KUNIT_RUN_ALL
Date: Thu, 7 May 2020 11:16:54 +0800 [thread overview]
Message-ID: <CABVgOS=Qybfh_oMGmCONUWqZ3FRcKrwPU1pooSv1SsFumaCFjg@mail.gmail.com> (raw)
In-Reply-To: <20200505102709.7964-1-anders.roxell@linaro.org>
On Tue, May 5, 2020 at 6:27 PM Anders Roxell <anders.roxell@linaro.org> wrote:
>
> This makes it easier to enable all KUnit fragments.
>
> Adding 'if !KUNIT_RUN_ALL' so individual test can be turned of if
> someone wants that even though KUNIT_RUN_ALL is enabled.
nit: Should this be "turned off" rather than "turned of" (and
"individual tests" rather than "individual test").
It _may_ be worth re-wording it to explain the "if !KUNIT_RUN_ALL"
change in more detail: that it's explicitly hiding the prompt if
KUNIT_RUN_ALL is enabled.
It's probably not worth redoing the patch just for this, but if you've
got to re-do all these to change KUNIT_RUN_ALL to KUNIT_ALL_TESTS or
similar, maybe.
>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Reviewed-by: David Gow <davidgow@google.com>
> ---
> lib/kunit/Kconfig | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/lib/kunit/Kconfig b/lib/kunit/Kconfig
> index 537f37bc8400..e6a60391fa6b 100644
> --- a/lib/kunit/Kconfig
> +++ b/lib/kunit/Kconfig
> @@ -15,7 +15,8 @@ menuconfig KUNIT
> if KUNIT
>
> config KUNIT_DEBUGFS
> - bool "KUnit - Enable /sys/kernel/debug/kunit debugfs representation"
> + bool "KUnit - Enable /sys/kernel/debug/kunit debugfs representation" if !KUNIT_RUN_ALL
> + default KUNIT_RUN_ALL
> help
> Enable debugfs representation for kunit. Currently this consists
> of /sys/kernel/debug/kunit/<test_suite>/results files for each
> @@ -23,7 +24,8 @@ config KUNIT_DEBUGFS
> run that occurred.
>
> config KUNIT_TEST
> - tristate "KUnit test for KUnit"
> + tristate "KUnit test for KUnit" if !KUNIT_RUN_ALL
> + default KUNIT_RUN_ALL
> help
> Enables the unit tests for the KUnit test framework. These tests test
> the KUnit test framework itself; the tests are both written using
> @@ -32,7 +34,8 @@ config KUNIT_TEST
> expected.
>
> config KUNIT_EXAMPLE_TEST
> - tristate "Example test for KUnit"
> + tristate "Example test for KUnit" if !KUNIT_RUN_ALL
> + default KUNIT_RUN_ALL
> help
> Enables an example unit test that illustrates some of the basic
> features of KUnit. This test only exists to help new users understand
> --
> 2.20.1
>
prev parent reply other threads:[~2020-05-07 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 10:27 [PATCH v2 2/6] kunit: default KUNIT_* fragments to KUNIT_RUN_ALL Anders Roxell
2020-05-07 3:16 ` David Gow [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='CABVgOS=Qybfh_oMGmCONUWqZ3FRcKrwPU1pooSv1SsFumaCFjg@mail.gmail.com' \
--to=davidgow@google.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=brendanhiggins@google.com \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=tytso@mit.edu \
/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).