From: Rob Herring <robh@kernel.org>
To: Conor.Dooley@microchip.com
Cc: Sergiu.Moga@microchip.com, Claudiu.Beznea@microchip.com,
linux-arm-kernel@lists.infradead.org,
UNGLinuxDriver@microchip.com, linux-spi@vger.kernel.org,
broonie@kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, Nicolas.Ferre@microchip.com,
Kavyasree.Kotagiri@microchip.com, alexandre.belloni@bootlin.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: spi: convert spi_atmel to json-schema
Date: Thu, 30 Jun 2022 15:12:36 -0600 [thread overview]
Message-ID: <20220630211236.GA3303869-robh@kernel.org> (raw)
In-Reply-To: <8191d9e3-88e9-c8fb-2544-d25d3a93d0a8@microchip.com>
On Wed, Jun 29, 2022 at 10:45:20PM +0000, Conor.Dooley@microchip.com wrote:
> On 29/06/2022 23:36, Rob Herring wrote:
> > On Wed, 29 Jun 2022 15:58:04 +0300, Sergiu Moga wrote:
> >> Convert SPI binding for Atmel/Microchip SoCs to Device Tree Schema
> >> format.
> >>
> >> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
> >> ---
> >> .../devicetree/bindings/spi/atmel,spi.yaml | 82 +++++++++++++++++++
> >> .../devicetree/bindings/spi/spi_atmel.txt | 36 --------
> >> 2 files changed, 82 insertions(+), 36 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/spi/atmel,spi.yaml
> >> delete mode 100644 Documentation/devicetree/bindings/spi/spi_atmel.txt
> >>
> >
> > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > Documentation/devicetree/bindings/spi/atmel,spi.example.dtb:0:0: /example-0/spi@fffcc000/mmc@0: failed to match any schema with compatible: ['mmc-spi-slot']
>
> My conversion of this should be in -next right?
I don't know, you tell me.
> Is this just an incorrect base for the bot, or am I missing
> something?
The bot runs on rc1.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Conor.Dooley@microchip.com
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
Kavyasree.Kotagiri@microchip.com, linux-kernel@vger.kernel.org,
Sergiu.Moga@microchip.com, UNGLinuxDriver@microchip.com,
broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-spi@vger.kernel.org, Claudiu.Beznea@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: spi: convert spi_atmel to json-schema
Date: Thu, 30 Jun 2022 15:12:36 -0600 [thread overview]
Message-ID: <20220630211236.GA3303869-robh@kernel.org> (raw)
In-Reply-To: <8191d9e3-88e9-c8fb-2544-d25d3a93d0a8@microchip.com>
On Wed, Jun 29, 2022 at 10:45:20PM +0000, Conor.Dooley@microchip.com wrote:
> On 29/06/2022 23:36, Rob Herring wrote:
> > On Wed, 29 Jun 2022 15:58:04 +0300, Sergiu Moga wrote:
> >> Convert SPI binding for Atmel/Microchip SoCs to Device Tree Schema
> >> format.
> >>
> >> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
> >> ---
> >> .../devicetree/bindings/spi/atmel,spi.yaml | 82 +++++++++++++++++++
> >> .../devicetree/bindings/spi/spi_atmel.txt | 36 --------
> >> 2 files changed, 82 insertions(+), 36 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/spi/atmel,spi.yaml
> >> delete mode 100644 Documentation/devicetree/bindings/spi/spi_atmel.txt
> >>
> >
> > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > Documentation/devicetree/bindings/spi/atmel,spi.example.dtb:0:0: /example-0/spi@fffcc000/mmc@0: failed to match any schema with compatible: ['mmc-spi-slot']
>
> My conversion of this should be in -next right?
I don't know, you tell me.
> Is this just an incorrect base for the bot, or am I missing
> something?
The bot runs on rc1.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-30 21:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:58 [PATCH] dt-bindings: spi: convert spi_atmel to json-schema Sergiu Moga
2022-06-29 12:58 ` Sergiu Moga
2022-06-29 13:23 ` Krzysztof Kozlowski
2022-06-29 13:23 ` Krzysztof Kozlowski
2022-06-29 15:01 ` Nicolas Ferre
2022-06-29 15:01 ` Nicolas Ferre
2022-06-30 6:07 ` Sergiu.Moga
2022-06-30 6:07 ` Sergiu.Moga
2022-06-30 5:59 ` Sergiu.Moga
2022-06-30 5:59 ` Sergiu.Moga
2022-06-29 14:12 ` Mark Brown
2022-06-29 14:12 ` Mark Brown
2022-06-29 22:36 ` Rob Herring
2022-06-29 22:36 ` Rob Herring
2022-06-29 22:45 ` Conor.Dooley
2022-06-29 22:45 ` Conor.Dooley
2022-06-30 21:12 ` Rob Herring [this message]
2022-06-30 21:12 ` Rob Herring
2022-06-30 22:22 ` Conor.Dooley
2022-06-30 22:22 ` Conor.Dooley
2022-07-01 7:41 ` Nicolas Ferre
2022-07-01 7:41 ` Nicolas Ferre
2022-07-01 7:50 ` Conor.Dooley
2022-07-01 7:50 ` Conor.Dooley
2022-07-01 7:56 ` Nicolas Ferre
2022-07-01 7:56 ` Nicolas Ferre
2022-06-30 6:05 ` Sergiu.Moga
2022-06-30 6:05 ` Sergiu.Moga
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=20220630211236.GA3303869-robh@kernel.org \
--to=robh@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Sergiu.Moga@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.