Subject: [PATCH V4 0/3] Add compatible for Mediatek MT8186

V4:
1. add "dt-bindings: spi: Convert spi-slave-mt27xx to json-schema" to
this series again.

v3:
1. Fix Rob review comment in v2.

v2:
1. Fix Rob review comment.
2. split spi-mt65xx & spi-slave-mt27xx to 2 patches.

Leilk Liu (3):
  dt-bindings: spi: Convert spi-slave-mt27xx to json-schema
  dt-bindings: spi: Convert spi-mt65xx to json-schema
  dt-bindings: spi: Add compatible for Mediatek MT8186

 .../bindings/spi/mediatek,spi-mt65xx.yaml     | 102 ++++++++++++++++++
 .../spi/mediatek,spi-slave-mt27xx.yaml        |  58 ++++++++++
 .../devicetree/bindings/spi/spi-mt65xx.txt    |  68 ------------
 .../bindings/spi/spi-slave-mt27xx.txt         |  33 ------
 4 files changed, 160 insertions(+), 101 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml
 create mode 100644 Documentation/devicetree/bindings/spi/mediatek,spi-slave-mt27xx.yaml
 delete mode 100644 Documentation/devicetree/bindings/spi/spi-mt65xx.txt
 delete mode 100644 Documentation/devicetree/bindings/spi/spi-slave-mt27xx.txt

--
2.18.0

On Tue, 25 Jan 2022 09:23:27 +0800, Leilk Liu wrote:
> Subject: [PATCH V4 0/3] Add compatible for Mediatek MT8186
> 
> V4:
> 1. add "dt-bindings: spi: Convert spi-slave-mt27xx to json-schema" to
> this series again.
> 
> v3:
> 1. Fix Rob review comment in v2.
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: spi: Convert spi-slave-mt27xx to json-schema
      commit: 60edd652005fe2931565f658f23f86d094f4c1f0
[2/3] dt-bindings: spi: Convert spi-mt65xx to json-schema
      commit: 08727dd751234bc878be64e60ea6f0d8ea0d54c0
[3/3] dt-bindings: spi: Add compatible for Mediatek MT8186
      commit: ccbc5d0a92c5f1d42d1a1635b53f1987821e9cdd

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