From: Rob Herring <robh@kernel.org>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
ludovic.desroches@microchip.com, broonie@kernel.org,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: spi: atmel,quadspi: Convert to json-schema
Date: Wed, 15 Dec 2021 11:04:54 -0600 [thread overview]
Message-ID: <YbogNtvbtypd41g5@robh.at.kernel.org> (raw)
In-Reply-To: <20211209122939.339810-2-tudor.ambarus@microchip.com>
On Thu, 09 Dec 2021 14:29:38 +0200, Tudor Ambarus wrote:
> Convert the Atmel QuadSPI controller Device Tree binding documentation
> to json-schema.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> .../bindings/spi/atmel,quadspi.yaml | 87 +++++++++++++++++++
> .../devicetree/bindings/spi/atmel-quadspi.txt | 37 --------
> 2 files changed, 87 insertions(+), 37 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
> delete mode 100644 Documentation/devicetree/bindings/spi/atmel-quadspi.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
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:[~2021-12-15 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 12:29 [PATCH 0/2] dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI Tudor Ambarus
2021-12-09 12:29 ` [PATCH 1/2] dt-bindings: spi: atmel,quadspi: Convert to json-schema Tudor Ambarus
2021-12-09 17:10 ` [PATCH 1/2] dt-bindings: spi: atmel, quadspi: " Rob Herring
2021-12-09 17:26 ` [PATCH 1/2] dt-bindings: spi: atmel,quadspi: " Tudor.Ambarus
2021-12-15 17:04 ` Rob Herring [this message]
2021-12-09 12:29 ` [PATCH 2/2] dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI Tudor Ambarus
2021-12-15 17:05 ` Rob Herring
2021-12-16 2:21 ` [PATCH 0/2] " Mark Brown
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=YbogNtvbtypd41g5@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@microchip.com \
/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;
as well as URLs for NNTP newsgroup(s).