aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/dev-tools
diff options
context:
space:
mode:
authorShuah Khan <skhan@linuxfoundation.org>2022-01-26 13:13:41 -0700
committerShuah Khan <skhan@linuxfoundation.org>2022-01-27 10:56:09 -0700
commitdede34b2c1a88e26f8353b433e381ea355f7258d (patch)
treeba2d9167529411decd4370700a5ad71a7f2f20d5 /Documentation/dev-tools
parent92d25637a3a45904292c93f1863c6bbda4e3e38f (diff)
downloadlinux-dede34b2c1a88e26f8353b433e381ea355f7258d.tar.gz
docs/kselftest: clarify running mainline tests on stables
Update the document to clarifiy support for running mainline kselftest on stable releases and the reasons for not removing test code that can test older kernels. Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'Documentation/dev-tools')
-rw-r--r--Documentation/dev-tools/kselftest.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/dev-tools/kselftest.rst b/Documentation/dev-tools/kselftest.rst
index dcefee707ccdc3..a833ecf12fbc1d 100644
--- a/Documentation/dev-tools/kselftest.rst
+++ b/Documentation/dev-tools/kselftest.rst
@@ -7,6 +7,14 @@ directory. These are intended to be small tests to exercise individual code
paths in the kernel. Tests are intended to be run after building, installing
and booting a kernel.
+Kselftest from mainline can be run on older stable kernels. Running tests
+from mainline offers the best coverage. Several test rings run mainline
+kselftest suite on stable releases. The reason is that when a new test
+gets added to test existing code to regression test a bug, we should be
+able to run that test on an older kernel. Hence, it is important to keep
+code that can still test an older kernel and make sure it skips the test
+gracefully on newer releases.
+
You can find additional information on Kselftest framework, how to
write new tests using the framework on Kselftest wiki: