From: Mason Zhang <[email protected]>
this patch update spi master bingdings for MT6893 SOC.
Change-Id: Iaa2840f7e89db83f9505302b50b449f8885a14c1
Signed-off-by: Mason Zhang <[email protected]>
---
Documentation/devicetree/bindings/spi/spi-mt65xx.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt b/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
index 4d0e4c15c4ea..2a24969159cc 100644
--- a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
+++ b/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
@@ -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
--
2.18.0
On Tue, Jun 29, 2021 at 06:13:11PM +0800, Mason Zhang wrote:
> Change-Id: Iaa2840f7e89db83f9505302b50b449f8885a14c1
Please don't include noise like this in upstream patch submissions.
On Tue, 29 Jun 2021 18:13:11 +0800, Mason Zhang wrote:
> 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