A couple of additional refactorings on top of the multi-CS support.
One is to make sure that the comment and the code are not disrupted
if additional changes come in the future and second one is f or the
sake of deduplication. In both cases it also makes indentation level
smaller in the affected pieces of the code.

No functional changes intended.

Andy Shevchenko (2):
  spi: Extract spi_toggle_csgpiod() helper for better maintanance
  spi: Introduce spi_for_each_valid_cs() in order of deduplication

 drivers/spi/spi.c | 63 +++++++++++++++++++++++++----------------------
 1 file changed, 33 insertions(+), 30 deletions(-)

-- 
2.43.0.rc1.1336.g36b5255a03ac

On Mon, 15 Apr 2024 22:31:18 +0300, Andy Shevchenko wrote:
> A couple of additional refactorings on top of the multi-CS support.
> One is to make sure that the comment and the code are not disrupted
> if additional changes come in the future and second one is f or the
> sake of deduplication. In both cases it also makes indentation level
> smaller in the affected pieces of the code.
> 
> No functional changes intended.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: Extract spi_toggle_csgpiod() helper for better maintanance
      commit: e81582c080ddec3359bc6726291e62a1ba8b7350
[2/2] spi: Introduce spi_for_each_valid_cs() in order of deduplication
      commit: d707530b1ea518e23c7aa7b50ee79231f2964da0

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