[PATCH v1 0/3] spi: Kconfig cleanups

Andy Shevchenko posted 3 patches 1 month, 1 week ago
drivers/spi/Kconfig | 364 ++++++++++++++++++++++----------------------
1 file changed, 179 insertions(+), 185 deletions(-)
[PATCH v1 0/3] spi: Kconfig cleanups
Posted by Andy Shevchenko 1 month, 1 week ago
With time the section order is diverged, put it back into order.

Andy Shevchenko (3):
  spi: Fix tab and space mixture in Kconfig
  spi: Drop redundant dependency on SPI_MASTER
  spi: Fix the section ordering in accordance with the comment

 drivers/spi/Kconfig | 364 ++++++++++++++++++++++----------------------
 1 file changed, 179 insertions(+), 185 deletions(-)

-- 
2.50.1
Re: [PATCH v1 0/3] spi: Kconfig cleanups
Posted by Mark Brown 4 weeks ago
On Fri, 21 Aug 2026 12:54:51 +0200, Andy Shevchenko wrote:
> spi: Kconfig cleanups
> 
> With time the section order is diverged, put it back into order.
> 
> Andy Shevchenko (3):
>   spi: Fix tab and space mixture in Kconfig
>   spi: Drop redundant dependency on SPI_MASTER
>   spi: Fix the section ordering in accordance with the comment
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: Fix tab and space mixture in Kconfig
      https://git.kernel.org/broonie/spi/c/dd007297551f
[2/3] spi: Drop redundant dependency on SPI_MASTER
      https://git.kernel.org/broonie/spi/c/4895d7068723
[3/3] spi: Fix the section ordering in accordance with the comment
      https://git.kernel.org/broonie/spi/c/d696b9109d23

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