Documentation/dev-tools/kunit/api/index.rst

Source file repositories/reference/linux-study-clean/Documentation/dev-tools/kunit/api/index.rst

File Facts

System: Linux kernel
Corpus path: Documentation/dev-tools/kunit/api/index.rst
Extension: .rst
Size: 869 bytes
Lines: 49
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

.. SPDX-License-Identifier: GPL-2.0

=============
API Reference
=============
.. toctree::
	:hidden:

	test
	resource
	functionredirection
	clk
	of
	platformdevice


This page documents the KUnit kernel testing API. It is divided into the
following sections:

Core KUnit API
==============

Documentation/dev-tools/kunit/api/test.rst

 - Documents all of the standard testing API

Documentation/dev-tools/kunit/api/resource.rst

 - Documents the KUnit resource API

Documentation/dev-tools/kunit/api/functionredirection.rst

 - Documents the KUnit Function Redirection API

Driver KUnit API
================

Documentation/dev-tools/kunit/api/clk.rst

 - Documents the KUnit clk API

Documentation/dev-tools/kunit/api/of.rst

 - Documents the KUnit device tree (OF) API

Documentation/dev-tools/kunit/api/platformdevice.rst

 - Documents the KUnit platform device API

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.