scripts/dtc/dt-style-selftest/bad/yaml-trailing-comment.yaml

File Facts

System

Linux kernel

Corpus path

scripts/dtc/dt-style-selftest/bad/yaml-trailing-comment.yaml

Extension

.yaml

Size

606 bytes

Lines

27

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-bad-trailing-comment.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Test fixture with properties out of order behind trailing comments

maintainers:
  - Test User <test@example.com>

properties:
  compatible:
    const: example,test-trailing-comment

required:
  - compatible

additionalProperties: false

examples:
  - |
    foo@0 {  /* the device node */
        reg = <0x0 0x4>;  /* registers */
        compatible = "example,test-trailing-comment";  // misplaced
    };

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.