From 0a83293322fde69f1fb4722bd3c79c2d52eef436 Mon Sep 17 00:00:00 2001 From: Dmitry Antipov Date: Fri, 23 Jan 2026 10:15:23 +0300 Subject: [PATCH] doc: development-process: add notice on testing Add testing notice to "Before creating patches" section. Suggested-by: Andy Shevchenko Signed-off-by: Dmitry Antipov Acked-by: Randy Dunlap Acked-by: Andy Shevchenko Signed-off-by: Jonathan Corbet Message-ID: <20260123071523.1392729-1-dmantipov@yandex.ru> --- Documentation/process/5.Posting.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst index 9999bcbdccc95..07d7dbed13ec6 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. -- 2.47.3