On Fri, 17 Nov 2023 20:10:53 +0530, Raag Jadav wrote: > Instead of comparing parameters for every supported mem_ops, only compare > on opcode match, which is relatively more efficient. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: intel: make mem_ops comparison unique to opcode match commit: 18a813a1f94abbab14248071ca551e491bbc2abe 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