scripts/dtc/dt-style-selftest/good/yaml-4space.yaml
Source file repositories/reference/linux-study-clean/scripts/dtc/dt-style-selftest/good/yaml-4space.yaml
File Facts
- System
- Linux kernel
- Corpus path
scripts/dtc/dt-style-selftest/good/yaml-4space.yaml- Extension
.yaml- Size
- 804 bytes
- Lines
- 42
- Domain
- Support Tooling And Documentation
- Bucket
- scripts
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- 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-only OR BSD-2-Clause
%YAML 1.2
---
$id: http://devicetree.org/schemas/test-good-4space.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Test fixture for dt-check-style
maintainers:
- Test User <test@example.com>
properties:
compatible:
const: example,test-4space
reg:
maxItems: 1
required:
- compatible
- reg
additionalProperties: false
examples:
- |
bus@10000 {
compatible = "simple-bus";
reg = <0x10000 0x1000>;
#address-cells = <1>;
#size-cells = <1>;
device@100 {
compatible = "example,test-4space";
reg = <0x100 0x10>;
};
device@200 {
compatible = "example,test-4space";
reg = <0x200 0x10>;
};
};
Annotation
- Atlas domain: Support Tooling And Documentation / scripts.
- 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.