Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] Unintended replacement of BNF notation `::=` with `:=`. --
commit a9fdd0b065eb5b6394a9c33ffba0fd5194e80115 Author: Krzysztof Kozlowski <[email protected]> dt-bindings: Drop incorrect usage of double '::' This commit cleans up device tree binding schemas by removing the redundant double colons at the end of descriptions inside YAML literal style blocks. Link: https://yaml.org/spec/1.2.2/#literal-style [1] > diff --git a/Documentation/devicetree/bindings/mux/mux-consumer.yaml > b/Documentation/devicetree/bindings/mux/mux-consumer.yaml > index 9e2d78a78e409..769243a2bf046 100644 > --- a/Documentation/devicetree/bindings/mux/mux-consumer.yaml > +++ b/Documentation/devicetree/bindings/mux/mux-consumer.yaml > @@ -13,8 +13,8 @@ description: | > Mux controller consumers should specify a list of mux controllers that they > want to use with a property containing a 'mux-ctrl-list': > > - mux-ctrl-list ::= <single-mux-ctrl> [mux-ctrl-list] > - single-mux-ctrl ::= <mux-ctrl-phandle> [mux-ctrl-specifier] > + mux-ctrl-list := <single-mux-ctrl> [mux-ctrl-list] > + single-mux-ctrl := <mux-ctrl-phandle> [mux-ctrl-specifier] [Severity: Low] Does this unintentionally change the standard Backus-Naur Form (BNF) ::= operator to :=? It looks like a global search-and-replace for :: might have accidentally caught these BNF production rules. -- Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
