Received-SPF: pass (google.com: domain of linux-kernel+bounces-38697-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, 
 Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh+dt@kernel.org>, 
 Conor Dooley <conor+dt@kernel.org>, 
 Sam Protsenko <semen.protsenko@linaro.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>, 
 Sylwester Nawrocki <s.nawrocki@samsung.com>, 
 Tomasz Figa <tomasz.figa@gmail.com>, Chanwoo Choi <cw00.choi@samsung.com>, 
 linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org, 
 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, 
 linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
In-Reply-To: <20240120012948.8836-1-semen.protsenko@linaro.org>
References: <20240120012948.8836-1-semen.protsenko@linaro.org>
Subject: Re: (subset) [PATCH 0/7] arm64: exynos: Enable SPI for Exynos850
Message-Id: <170619136385.38074.4377918274781683592.b4-ty@kernel.org>
Date: Thu, 25 Jan 2024 14:02:43 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Fri, 19 Jan 2024 19:29:41 -0600, Sam Protsenko wrote:
> This series enables SPI for Exynos850 SoC. The summary:
> 
>   1. Enable PDMA, it's needed for SPI (dts, clk)
>   2. Propagate SPI src clock rate change up to DIV clocks, to make it
>      possible to change SPI frequency (clk driver)
>   3. Add Exynos850 support in SPI driver
>   4. Add SPI nodes to Exynos850 SoC dtsi
> 
> [...]

Applied to

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

Thanks!

[2/7] dt-bindings: spi: samsung: Add Exynos850 SPI
      commit: 737cf74b38007fd5d5d2f15d4d4bc16e5f1cbfed
[5/7] spi: s3c64xx: Add Exynos850 support
      commit: 0229278bf33ea69cc1bba12c287f173e9b18c1f8

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