Skip to content

Commit dede34b

Browse files
committed
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 <[email protected]>
1 parent 92d2563 commit dede34b

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

Documentation/dev-tools/kselftest.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,14 @@ directory. These are intended to be small tests to exercise individual code
77
paths in the kernel. Tests are intended to be run after building, installing
88
and booting a kernel.
99

10+
Kselftest from mainline can be run on older stable kernels. Running tests
11+
from mainline offers the best coverage. Several test rings run mainline
12+
kselftest suite on stable releases. The reason is that when a new test
13+
gets added to test existing code to regression test a bug, we should be
14+
able to run that test on an older kernel. Hence, it is important to keep
15+
code that can still test an older kernel and make sure it skips the test
16+
gracefully on newer releases.
17+
1018
You can find additional information on Kselftest framework, how to
1119
write new tests using the framework on Kselftest wiki:
1220

0 commit comments

Comments
 (0)