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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <163962128492.2075495.3678727080606971257.b4-ty@kernel.org>
Date:   Thu, 16 Dec 2021 02:21:24 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Tudor Ambarus <tudor.ambarus@...rochip.com>, robh+dt@...nel.org
Cc:     linux-spi@...r.kernel.org, nicolas.ferre@...rochip.com,
        ludovic.desroches@...rochip.com,
        linux-arm-kernel@...ts.infradead.org,
        alexandre.belloni@...tlin.com, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] dt-bindings: spi: atmel,quadspi: Define sama7g5 QSPI

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