summaryrefslogtreecommitdiff
path: root/lib/kunit/.kunitconfig
diff options
context:
space:
mode:
authorDaniel Latypov <dlatypov@google.com>2021-02-23 01:52:41 +0300
committerShuah Khan <skhan@linuxfoundation.org>2021-04-02 23:14:36 +0300
commit9854781dba371dda22880fc6acac7688fb5e2bae (patch)
tree58d81436a1f95e48c98c88a8abe3ba280497f284 /lib/kunit/.kunitconfig
parentacd976253c0ce98e92c766bd720bb00e4c2facb6 (diff)
downloadlinux-9854781dba371dda22880fc6acac7688fb5e2bae.tar.xz
kunit: tool: make --kunitconfig accept dirs, add lib/kunit fragment
TL;DR $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit Per suggestion from Ted [1], we can reduce the amount of typing by assuming a convention that these files are named '.kunitconfig'. In the case of [1], we now have $ ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4 Also add in such a fragment for kunit itself so we can give that as an example more close to home (and thus less likely to be accidentally broken). [1] https://lore.kernel.org/linux-ext4/YCNF4yP1dB97zzwD@mit.edu/ Signed-off-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: David Gow <davidgow@google.com> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'lib/kunit/.kunitconfig')
-rw-r--r--lib/kunit/.kunitconfig3
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/kunit/.kunitconfig b/lib/kunit/.kunitconfig
new file mode 100644
index 000000000000..9235b7d42d38
--- /dev/null
+++ b/lib/kunit/.kunitconfig
@@ -0,0 +1,3 @@
+CONFIG_KUNIT=y
+CONFIG_KUNIT_TEST=y
+CONFIG_KUNIT_EXAMPLE_TEST=y