Message ID | 20240530151117.1130792-1-andriy.shevchenko@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: pxa2xx: Get rid of an additional layer in PCI driver | expand |
On Thu, 30 May 2024 18:09:56 +0300, Andy Shevchenko wrote: > SPI PXA2xx main driver is a compound of a core library and > a platform driver code. Decoupling that allows to eventually > get rid of an additional layer of devices hierarchy in PCI driver. > There are also precursor cleanups. > > In v2: > - made better handling of pxa_ssp_free() calls > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [01/11] spi: pxa2xx: Wrap pxa_ssp_request() to be device managed resource commit: a2fca8f2e242b3cdfed2a15084e733348ef68509 [02/11] spi: pxa2xx: Reorganize the SSP type retrieval commit: 8aa5062e26054b8c081d5bba930baac4faadd1b0 [03/11] spi: pxa2xx: Remove no more needed driver data commit: 7b0f2c1050643c4793e6eae0246a8de3b22c950a [04/11] spi: pxa2xx: Remove hard coded number of chip select pins commit: c1b93986dfb2a31b0528fe929d574843801089f5 [05/11] spi: pxa2xx: Utilise temporary variable for struct device commit: c65174fdb2f7fe83ee515966c08de9a990e722f9 [06/11] spi: pxa2xx: Print DMA burst size only when DMA is enabled commit: 9b328f5f5c921ec83e1765075b82e6cc05e576b9 [07/11] spi: pxa2xx: Remove duplicate check commit: 560fb06df2fd250004a1cac079717dbe7f863ff2 [08/11] spi: pxa2xx: Remove superflous check for Intel Atom SoCs commit: 75bfdccaecf96189318b29100b880c416d89ed46 [09/11] spi: pxa2xx: Extract pxa2xx_spi_platform_*() callbacks commit: 20ade9b9771c80eb58eb42ccd0a48ba24bdc3c4f [10/11] spi: pxa2xx: Move platform driver to a separate file commit: 3d8f037fbcab53e03ab2ef18a66f202be3653d50 [11/11] spi: pxa2xx: Convert PCI driver to use spi-pxa2xx code directly commit: cc160697a576150975280a4b5394fe9c70700503 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