summaryrefslogtreecommitdiff
path: root/rust/kernel/alloc/kvec/errors.rs
diff options
context:
space:
mode:
authorKrzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>2026-09-15 19:03:50 +0200
committerRob Herring (Arm) <robh@kernel.org>2026-09-16 15:17:07 -0500
commite97e9becf957216855a6b182ca5c1d0bc5e5065d (patch)
tree724a131e1f06bfc7c8ff8111a9195f4a58c3ae9b /rust/kernel/alloc/kvec/errors.rs
parent897e4c0de6e6fda41815ae0457db0e254fc67821 (diff)
dtc: dt-check-style: Properly detect comments in multi-line properties
Code classifying given line exits on first condition match, thus a line consisting only of a comment in a continued (multi-line) property, like: interrupts = <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>, /* Performance counter interrupts */ <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>; was treated as a comment-line line, not as continuation, leading to false positive warnings of invalid indentation: arch/arm64/boot/dts/tesla/fsd.dtsi:456: [indent-consistent] indent mismatch (expected depth 3 * '\t') This needs two related fixes: 1. Move the judgment as a LineType.CONTINUATION earlier before one classifying as a comment 2. Check the comment-stripped DtsLine.code, not DtsLine.stripped, to verify if it is a continuation. Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> Link: https://patch.msgid.link/20260915-b4-dts-style-checker-continued-lines-v4-6-5b8e09b11ef2@oss.qualcomm.com Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Diffstat (limited to 'rust/kernel/alloc/kvec/errors.rs')
0 files changed, 0 insertions, 0 deletions