Re: [PATCH] doc: development-process: add notice on testing

[Andy Shevchenko <andriy.shevchenko@intel.com>]

On Thu, Jan 22, 2026 at 02:15:25PM +0300, Dmitry Antipov wrote:
> Add testing notice to "Before creating patches" section.

Acked-by: Andy Shevchenko <andriy.shevchenko@intel.com>

Thanks!

I may confirm that lib/ is indeed a hotspot for treewide users and breaking
anything in lib/ almost always break at least a couple of users sometimes in
unexpected places. That's why the test cases are mandatory for a new feature
that will be reside in lib/.

> --- a/Documentation/process/5.Posting.rst
> +++ b/Documentation/process/5.Posting.rst

>   - 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 frameworks like KUnit, and include them as a separate member
> +   of your series (see the next section on what about the series is).
> +   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.

-- 
With Best Regards,
Andy Shevchenko