From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kavyasree.Kotagiri@microchip.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com,
krzysztof.kozlowski+dt@linaro.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, Claudiu.Beznea@microchip.com
Subject: Re: [PATCH v2 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema
Date: Thu, 16 Jun 2022 06:47:36 -0700 [thread overview]
Message-ID: <5abc998e-fea1-791b-3068-334d927af63d@linaro.org> (raw)
In-Reply-To: <CO1PR11MB4865A1D77AAD30410D8A815792AC9@CO1PR11MB4865.namprd11.prod.outlook.com>
On 16/06/2022 02:20, Kavyasree.Kotagiri@microchip.com wrote:
>>
>> Yes. This is how you did it in previous patchsets.
>>
> I did so in v3 series, but below errors are reported on 1/3 patch:
> dtschema/dtc warnings/errors:
> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml: properties:compatible:enum: 'atmel,sama5d2-flexcom' is not of type 'array'
I don't remember it but it's a simple fix of syntax.
Documentation/devicetree/bindings/arm/arm,cci-400.yaml
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-16 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:47 [PATCH v2 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-06-07 14:47 ` [PATCH v2 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema Kavyasree Kotagiri
2022-06-08 7:25 ` Claudiu.Beznea
2022-06-08 8:34 ` Krzysztof Kozlowski
2022-06-08 9:31 ` Kavyasree.Kotagiri
2022-06-08 9:33 ` Krzysztof Kozlowski
2022-06-16 9:20 ` Kavyasree.Kotagiri
2022-06-16 13:47 ` Krzysztof Kozlowski [this message]
2022-06-08 13:45 ` Rob Herring
2022-06-07 14:47 ` [PATCH v2 2/3] dt-bindings: mfd: atmel,flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-06-07 14:47 ` [PATCH v2 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-06-08 7:35 ` Claudiu.Beznea
2022-06-08 8:20 ` Kavyasree.Kotagiri
2022-06-08 14:17 ` Claudiu.Beznea
2022-06-09 5:18 ` Kavyasree.Kotagiri
2022-06-09 13:34 ` Kavyasree.Kotagiri
2022-06-10 9:06 ` Claudiu.Beznea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5abc998e-fea1-791b-3068-334d927af63d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®