[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168970600997.94192.11376983705102685200.b4-ty@kernel.org>
Date: Tue, 18 Jul 2023 19:46:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
Chris Paterson <Chris.Paterson2@...esas.com>,
Biju Das <biju.das@...renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
linux-renesas-soc@...r.kernel.org
Subject: Re: (subset) [PATCH 00/10] spi: rzv2m-csi: Code refactoring
On Sat, 15 Jul 2023 02:03:57 +0100, Fabrizio Castro wrote:
> this series is to follow up on Geert and Andy feedback:
> https://patchwork.kernel.org/project/linux-renesas-soc/patch/20230622113341.657842-4-fabrizio.castro.jz@renesas.com/
>
> Thanks,
> Fab
>
> Fabrizio Castro (10):
> spi: rzv2m-csi: Add missing include
> spi: rzv2m-csi: Adopt HZ_PER_MHZ for max spi clock
> spi: rzv2m-csi: Rework CSI_CKS_MAX definition
> spi: rzv2m-csi: Leave readl_poll_timeout calls for last
> spi: rzv2m-csi: Replace unnecessary ternary operators
> spi: rzv2m-csi: Squash timing settings into one statement
> spi: rzv2m-csi: Switch to using {read,write}s{b,w}
> spi: rzv2m-csi: Improve data types and alignment
> spi: rzv2m-csi: Get rid of the x_trg{_words} tables
> spi: rzv2m-csi: Make use of device_set_node
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[01/10] spi: rzv2m-csi: Add missing include
commit: f572ba797c639c9b1705908d3f5d71ed7c3f53e0
[02/10] spi: rzv2m-csi: Adopt HZ_PER_MHZ for max spi clock
commit: 74e27ce8d23c3aeb1a9fdcaf6261462506bbbfc3
[03/10] spi: rzv2m-csi: Rework CSI_CKS_MAX definition
commit: aecf9fbdb7a4dc6d83e8d9984c8d9dc074d8ea2e
[04/10] spi: rzv2m-csi: Leave readl_poll_timeout calls for last
commit: 2ed2699f58891c72fcd462129345d09424f986c5
[05/10] spi: rzv2m-csi: Replace unnecessary ternary operators
commit: 9f5ac599801c0f7c0969fa94c638265ed988b9bc
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