On Wed, 20 Apr 2022 17:56:15 +0200, Matthias Schiffer wrote: > As suggested, this removes the whole cqspi_set_protocol() function, as it > is not actually needed: > > - Checks for unsupported operations are already handled by supports_op(), > removing the need to distinguish DTR and non-DTR modes in the buswidth > setup > - supports_op() ensures that the DTR flags match for all relevant parts of > an operation, so op->cmd.dtr can be used instead of copying the flag to > the cqspi_flash_pdata > - The logic in cqspi_set_protocol() is moved to cqspi_calc_rdreg() and > cqspi_write_setup() (with a helper macro CQSPI_OP_WIDTH()) > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/2] spi: cadence-quadspi: drop cqspi_set_protocol() commit: 28ac902aedd18abf4faf8816b1bea6623d0e9509 [2/2] spi: cadence-quadspi: allow operations with cmd/addr buswidth >1 commit: 1aeda0966693574c07c5fa72adf41be43d491f96 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