On Wed, 17 Jul 2019, at 00:35, Rob Herring wrote: > On Mon, Jul 15, 2019 at 5:17 PM Joel Stanley <joel@xxxxxxxxx> wrote: > > > > On Mon, 15 Jul 2019 at 22:37, Rob Herring <robh@xxxxxxxxxx> wrote: > > > > > > The Aspeed pinctl schema have errors in the 'compatible' schema: > > > > > > Documentation/devicetree/bindings/pinctrl/aspeed,ast2400-pinctrl.yaml: \ > > > properties:compatible:enum: ['aspeed', 'ast2400-pinctrl', 'aspeed', 'g4-pinctrl'] has non-unique elements > > > Documentation/devicetree/bindings/pinctrl/aspeed,ast2500-pinctrl.yaml: \ > > > properties:compatible:enum: ['aspeed', 'ast2500-pinctrl', 'aspeed', 'g5-pinctrl'] has non-unique elements > > > > > > Flow style sequences have to be quoted if the vales contain ','. Fix > > > this by using the more common one line per entry formatting. > > > > > > > > properties: > > > compatible: > > > - enum: [ aspeed,ast2400-pinctrl, aspeed,g4-pinctrl ] > > > + enum: > > > + - aspeed,ast2400-pinctrl > > > + - aspeed,g4-pinctrl > > > > Thanks for the fix. However, we've standardised on the first form for > > all of our device trees, so we can drop the second compatible string > > from the bindings. > > Doing that would introduce validation warnings until the dts file is > updated. So we still need this change until that happens. My series takes care of that. Andrew