Re: [PATCH v2] doc: development-process: add notice on testing
From: Randy Dunlap <hidden>
Date: 2026-01-23 07:19:48
Also in:
workflows
On 1/22/26 11:15 PM, Dmitry Antipov wrote:
Add testing notice to "Before creating patches" section. Suggested-by: Andy Shevchenko <redacted> Signed-off-by: Dmitry Antipov <redacted>
Acked-by: Randy Dunlap <redacted> Andy also Acked it. I think you could/should include his Ack here as well. Thanks.
quoted hunk ↗ jump to hunk
--- v2: adjust spelling and wording according to Randy --- 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 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.
-- ~Randy