release_notes.rst: tentative section for 5.17

We have a critical mass of new patches that got Reviewed-by's from

These might not make it into 5.17, but having these features listed here
would be a good way to boost their visibility, regardless of what
version they finally end up going in.

Change-Id: I0012fc8e9c4593ba4d2283905395633b1908a726
Signed-off-by: Daniel Latypov <>
1 file changed
tree: 2ade91672c53691b22863cc245e55bf1c1c0057a
  1. development/
  2. statics/
  3. third_party/
  4. usage/
  5. .gitignore
  10. index.rst
  12. Makefile
  13. mocking.rst
  14. press.rst
  16. release_notes.rst

KUnit Documentation

KUnit is a lightweight unit testing and mocking framework for the Linux kernel. These tests are able to be run locally on a developer’s workstation without a VM or special hardware.

KUnit is heavily inspired by JUnit, Python’s unittest.mock, and Googletest/Googlemock for C++. KUnit defines a way to mock out C style classes and functions and create expectations on methods called within the code under test.

This is a repository to host the source for the KUnit documentation.

NOTE: There is an important distinction between KUnit‘s documentation source and it’s documentation site. As a project meant primarily to serve the development of the Linux kernel, a significant portion of our code and documentation reside in the Linux kernel codebase. Consequently, the documentation that does not live in the Linux kernel follows many of the conventions of the Linux kernel. One of these conventions is that we use Sphinx for all of our documentation. Thus, because Sphinx requires documentation to be compiled from its source files, we must have a repository for all the Sphinx source files and a separate repository for all of the generated output files to actually host the site. This is the repository for the source.

Where is the code?

How to build documentation

Documentation can be built by running:

make html

How to update the documentation

Our documentation is hosted at The documentation may be updated by building the documentation as described above, and then:


You can copy the files over without committing and pushing the files with:

./ --no-commit