On Tue, 06 Feb 2024 14:06:46 -0600, David Lechner wrote: > The __spi_split_transfer_maxsize() function has a gpf argument to allow > callers to specify the type of memory allocation that needs to be used. > However, this function only allocates struct spi_transfer and is not > intended to be used from atomic contexts so this type should always be > GFP_KERNEL, so we can just drop the argument. > > Some callers of these functions also passed GFP_DMA, but since only > struct spi_transfer is allocated and not any tx/rx buffers, this is > not actually necessary and is removed in this commit. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: drop gpf arg from __spi_split_transfer_maxsize() commit: c0c0293cf7a0f21ef461956d44e4add718574f3f 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