Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
doc: development-process: add notice on testing
Add testing notice to "Before creating patches" section.
Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Andy Shevchenko <andriy.shevchenko@intel.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260123071523.1392729-1-dmantipov@yandex.ru>
authored by
Dmitry Antipov
and committed by
Jonathan Corbet
0a832933
64e4882c
+6
-1
+6
-1
Documentation/process/5.Posting.rst
+6
-1
Documentation/process/5.Posting.rst
···
40
40
- Test the code to the extent that you can. Make use of the kernel's
41
41
debugging tools, ensure that the kernel will build with all reasonable
42
42
combinations of configuration options, use cross-compilers to build for
43
-
different architectures, etc.
43
+
different architectures, etc. Add tests, likely using an existing
44
+
testing framework like KUnit, and include them as a separate member
45
+
of your series (see the next section for more about patch series).
46
+
Note that this may be mandatory when affecting some subsystems. For
47
+
example, library functions (resides under lib/) are extensively used
48
+
almost everywhere and expected to be tested appropriately.
44
49
45
50
- Make sure your code is compliant with the kernel coding style
46
51
guidelines.