mbox series

[0/2] dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI

Message ID 20211209122939.339810-1-tudor.ambarus@microchip.com (mailing list archive)
Headers show
Series dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI | expand

Message

Tudor Ambarus Dec. 9, 2021, 12:29 p.m. UTC 
Convert the Atmel QuadSPI controller Device Tree binding documentation
to json-schema. Define sama7g5 QSPI.

After the conversion to yaml, make dtbs_check reavealed a problem
that was fixed with:
https://lore.kernel.org/lkml/20211209102542.254153-1-tudor.ambarus@microchip.com/

Tudor Ambarus (2):
  dt-bindings: spi: atmel,quadspi: Convert to json-schema
  dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI

 .../bindings/spi/atmel,quadspi.yaml           | 99 +++++++++++++++++++
 .../devicetree/bindings/spi/atmel-quadspi.txt | 37 -------
 2 files changed, 99 insertions(+), 37 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
 delete mode 100644 Documentation/devicetree/bindings/spi/atmel-quadspi.txt

Comments

Mark Brown Dec. 16, 2021, 2:21 a.m. UTC | #1 
On Thu, 9 Dec 2021 14:29:37 +0200, Tudor Ambarus wrote:
> Convert the Atmel QuadSPI controller Device Tree binding documentation
> to json-schema. Define sama7g5 QSPI.
> 
> After the conversion to yaml, make dtbs_check reavealed a problem
> that was fixed with:
> https://lore.kernel.org/lkml/20211209102542.254153-1-tudor.ambarus@microchip.com/
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] dt-bindings: spi: atmel,quadspi: Convert to json-schema
      commit: 001a41d2a7061694fa31accdbc2013bb5c5d83b5
[2/2] dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI
      commit: 77850bda360dd9b389d5064c64b79467d613c3d6

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark