summaryrefslogtreecommitdiff
path: root/Documentation/process
diff options
context:
space:
mode:
authorDmitry Antipov <dmantipov@yandex.ru>2026-01-23 10:15:23 +0300
committerJonathan Corbet <corbet@lwn.net>2026-02-02 10:02:05 -0700
commit0a83293322fde69f1fb4722bd3c79c2d52eef436 (patch)
tree648abb94a5e8b69122f6f5012cfb3fec63417e12 /Documentation/process
parent64e4882c8228b07c57e75f510b8c5d7ff46e4edc (diff)
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>
Diffstat (limited to 'Documentation/process')
-rw-r--r--Documentation/process/5.Posting.rst7
1 files changed, 6 insertions, 1 deletions
diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst
index 9999bcbdccc9..07d7dbed13ec 100644
--- a/Documentation/process/5.Posting.rst
+++ b/Documentation/process/5.Posting.rst
@@ -40,7 +40,12 @@ sending patches to the development community. These include:
- Test the code to the extent that you can. Make use of the kernel's
debugging tools, ensure that the kernel will build with all reasonable
combinations of configuration options, use cross-compilers to build for
- different architectures, etc.
+ different architectures, etc. Add tests, likely using an existing
+ testing framework like KUnit, and include them as a separate member
+ of your series (see the next section for more about patch series).
+ Note that this may be mandatory when affecting some subsystems. For
+ example, library functions (resides under lib/) are extensively used
+ almost everywhere and expected to be tested appropriately.
- Make sure your code is compliant with the kernel coding style
guidelines.