Skip to contentSkip to conversation

spi: mediatek: update spi master bingdings for MT6893 SOC

PATCH In review Mason Zhang 2 participants 3 messages Jun 29, 2021 – Jul 12, 2021

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 2/2 spi: mediatek: update spi master bingdings for MT6893 SOC

From: Mason Zhang <[email protected]>

this patch update spi master bingdings for MT6893 SOC.

Change-Id Iaa2840f7e89db83f9505302b50b449f8885a14c1
---
 Documentation/devicetree/bindings/spi/spi-mt65xx.txt | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/spi/spi-mt65xx.txt +1 -0
index 4d0e4c15c4ea..2a24969159cc 100644
@@ -11,6 +11,7 @@ Required properties:
     - mediatek,mt8135-spi: for mt8135 platforms
     - mediatek,mt8173-spi: for mt8173 platforms
     - mediatek,mt8183-spi: for mt8183 platforms
+    - mediatek,mt6893-spi: for mt6893 platforms
     - "mediatek,mt8192-spi", "mediatek,mt6765-spi": for mt8192 platforms
     - "mediatek,mt8195-spi", "mediatek,mt6765-spi": for mt8195 platforms
     - "mediatek,mt8516-spi", "mediatek,mt2712-spi": for mt8516 platforms
Signature · 1 line
2.18.0
maintainer
#1 lore raw
Quoted 1 line · Mason Zhang

Change-Id: Iaa2840f7e89db83f9505302b50b449f8885a14c1

Please don't include noise like this in upstream patch submissions.

maintainer
#2 lore raw
In reply to Mason Zhang
Quoted 1 line · Mason Zhang

this patch update spi master bingdings for MT6893 SOC.

Applied to

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

Thanks!

[2/2] spi: mediatek: update spi master bingdings for MT6893 SOC

      commit: 3522d9aa19285bbff14da20cb3481e36ef4835fd

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