Documentation/dev-tools/index.rst

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

File Facts

System: Linux kernel
Corpus path: Documentation/dev-tools/index.rst
Extension: .rst
Size: 906 bytes
Lines: 43
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

================================
Development tools for the kernel
================================

This document is a collection of documents about development tools that can
be used to work on the kernel. For now, the documents have been pulled
together without any significant effort to integrate them into a coherent
whole; patches welcome!

A brief overview of testing-specific tools can be found in
Documentation/dev-tools/testing-overview.rst

Tools that are specific to debugging can be found in
Documentation/process/debugging/index.rst

.. toctree::
   :caption: Table of contents
   :maxdepth: 2

   testing-overview
   checkpatch
   clang-format
   coccinelle
   context-analysis
   sparse
   kcov
   gcov
   kasan
   kmsan
   ubsan
   kmemleak
   kcsan
   lkmm/index
   kfence
   kselftest
   kunit/index
   ktap
   checkuapi
   gpio-sloppy-logic-analyzer
   autofdo
   propeller
   container

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.