| Message ID | 20210326130034.15231-1-p.yadav@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Convert Cadence QSPI bindings to yaml | expand |
On Fri, 26 Mar 2021 18:30:30 +0530, Pratyush Yadav wrote: > This series picks up Ramuthevar's effort on converting the Cadence QSPI > bindings to yaml [0]. During the conversion process, I discovered that > some TI device tree files were not using the compatible correctly. Those > are fixed in patches 1-3. > > [0] https://patchwork.kernel.org/project/spi-devel-general/patch/20201116031003.19062-6-vadivel.muruganx.ramuthevar@linux.intel.com/ > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [4/4] dt-bindings: spi: Convert cadence-quadspi.txt to cadence-quadspi.yaml commit: e54338004c032b0bb556c7a56db8688454b6587e 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
On Fri, 26 Mar 2021 18:30:30 +0530, Pratyush Yadav wrote: > This series picks up Ramuthevar's effort on converting the Cadence QSPI > bindings to yaml [0]. During the conversion process, I discovered that > some TI device tree files were not using the compatible correctly. Those > are fixed in patches 1-3. > > [0] https://patchwork.kernel.org/project/spi-devel-general/patch/20201116031003.19062-6-vadivel.muruganx.ramuthevar@linux.intel.com/ > > [...] Hi Pratyush Yadav, I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/4] arm64: dts: ti: k3-j721e-mcu: Fix ospi compatible commit: f1b6f6e7f595ed66ba5f5d628df3d259218d584b [2/4] arm64: dts: ti: k3-j7200-mcu: Fix ospi compatible commit: 0e941f496a8bdc47d34199c17f81b09b0dbe14ae [3/4] arm64: dts: ti: k3-am64-main: Fix ospi compatible commit: 112e5934ff3a7505e583365213a27f990922b76b All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant 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. [1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git