dt-bindings: thermal: qcom-tsens: Remove invalid tab character
Rob Herring (Arm)
maintainerPATCH 1/1 dt-bindings: thermal: qcom-tsens: Remove invalid tab character
Commit 1ee90870ce79 ("dt-bindings: thermal: tsens: Add QCS8300 compatible") uses a tab character which is illegal in YAML (at the beginning of a line). The original patch was correct, so this got corrupted when applied.
---
Linus, Can you please apply this directly as your tree and next are broken and that breaks all my automated testing. I raised the issue with Daniel on Mon, but haven't gotten any response.
--- Documentation/devicetree/bindings/thermal/qcom-tsens.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/thermal/qcom-tsens.yaml +1 -1
@@ -61,7 +61,7 @@ properties: - qcom,msm8996-tsens - qcom,msm8998-tsens - qcom,qcm2290-tsens - - qcom,qcs8300-tsens + - qcom,qcs8300-tsens - qcom,qcs615-tsens - qcom,sa8255p-tsens - qcom,sa8775p-tsens
Signature · 1 line
2.51.0
Linus Torvalds
AppliedQuoted 4 lines · Rob Herring (Arm)
Commit
1ee90870ce79("dt-bindings: thermal: tsens: Add QCS8300 compatible") uses a tab character which is illegal in YAML (at the beginning of a line).
Applied.
But I want to object to the garbage that is 'yaml' and 'invisible whitespace has semantics'.
Maybe we can have a "kernel yaml" that just turns tabs into spaces with 'expand -t 8' and make the rule be that kernel yaml files don't have to participate in the mindless garbage that is "yaml by the specs".
Yes, I know it matters for 'make'. That was a mistake too. But at least we could *fix* the braindamage that is yaml, and we already have a defined tab width for the kernel anyway.
Linus