[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175340005103.192002.4970048454076941668.b4-ty@kernel.org>
Date: Fri, 25 Jul 2025 00:34:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>
Cc: linux-spi@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Biju Das <biju.das.jz@...renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH v2 0/3] Add RSPI support for RZ/V2H
On Fri, 04 Jul 2025 17:20:33 +0100, Fabrizio Castro wrote:
> This series adds support for the Renesas RZ/V2H RSPI IP.
>
> Cheers,
> Fab
>
> v1->v2:
> * Addressed build error reported by the kernel test robot.
> * Addressed comments from Biju in driver patch.
> * Addressed comments from Mark in driver patch.
> * The clock patch has been accepted, therefore it's not been included
> in this version.
> * The defconfig patch has been accepted (pending acceptance of the
> driver), therefore it's not been included in this version.
> * The device tree patch has been accepted (pending acceptance of
> the dt-bindings patch), therefore it's not been included in this
> version.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] spi: dt-bindings: Document the RZ/V2H(P) RSPI
commit: 44b91d61c505863b8ae90b7094aee5ca0dce808f
[2/3] spi: Add driver for the RZ/V2H(P) RSPI IP
commit: 8b61c8919dff080d83415523cd68f2fef03ccfc7
[3/3] MAINTAINERS: Add entries for the RZ/V2H(P) RSPI
(no commit info)
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
Powered by blists - more mailing lists