scripts/dtc/dt-style-selftest/expected/yaml-child-addr-order.yaml.txt
Source file repositories/reference/linux-study-clean/scripts/dtc/dt-style-selftest/expected/yaml-child-addr-order.yaml.txt
File Facts
- System
- Linux kernel
- Corpus path
scripts/dtc/dt-style-selftest/expected/yaml-child-addr-order.yaml.txt- Extension
.txt- Size
- 118 bytes
- Lines
- 3
- Domain
- Support Tooling And Documentation
- Bucket
- scripts
- 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
# mode=strict
bad/yaml-child-addr-order.yaml:37: example 0 [child-address-order] child node @100 out of address orderAnnotation
- 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.