[v1,0/5] spi: pxa2xx: Cleanup (part 2)

Message

Andy Shevchenko April 3, 2024, 5:06 p.m. UTC

Here is the additional cleanup of the driver based on the fact of
the linux/spi/pxa2xx_spi.h being a local (to drivers/spi/) header.
This means it's based on top of "spi: pxa2xx: Drop linux/spi/pxa2xx_spi.h"
([e-mail]).

Andy Shevchenko (5):
  spi: pxa2xx: Move number of CS pins validation out of condition
  spi: pxa2xx: Drop struct pxa2xx_spi_chip
  spi: pxa2xx: Remove DMA parameters from struct chip_data
  spi: pxa2xx: Remove timeout field from struct chip_data
  spi: pxa2xx: Don't provide struct chip_data for others

 drivers/spi/spi-pxa2xx-dma.c | 27 +----------
 drivers/spi/spi-pxa2xx.c     | 92 +++++++++---------------------------
 drivers/spi/spi-pxa2xx.h     | 31 ------------
 3 files changed, 25 insertions(+), 125 deletions(-)

Comments

Mark Brown April 15, 2024, 11:43 p.m. UTC | #1

On Wed, 03 Apr 2024 20:06:34 +0300, Andy Shevchenko wrote:
> Here is the additional cleanup of the driver based on the fact of
> the linux/spi/pxa2xx_spi.h being a local (to drivers/spi/) header.
> This means it's based on top of "spi: pxa2xx: Drop linux/spi/pxa2xx_spi.h"
> ([e-mail]).
> 
> Andy Shevchenko (5):
>   spi: pxa2xx: Move number of CS pins validation out of condition
>   spi: pxa2xx: Drop struct pxa2xx_spi_chip
>   spi: pxa2xx: Remove DMA parameters from struct chip_data
>   spi: pxa2xx: Remove timeout field from struct chip_data
>   spi: pxa2xx: Don't provide struct chip_data for others
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: pxa2xx: Move number of CS pins validation out of condition
      commit: df3431fd379dcc3b231bd109a55948c27474478d
[2/5] spi: pxa2xx: Drop struct pxa2xx_spi_chip
      (no commit info)
[3/5] spi: pxa2xx: Remove DMA parameters from struct chip_data
      (no commit info)
[4/5] spi: pxa2xx: Remove timeout field from struct chip_data
      (no commit info)
[5/5] spi: pxa2xx: Don't provide struct chip_data for others
      (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