Re: [PATCH v1] spi: mux: Fix mux interaction with fast path optimisations

[Mark Brown <broonie@xxxxxxxxxx>]

On Thu, 1 Sep 2022 13:07:32 +0100, Mark Brown wrote:
> The spi-mux driver is rather too clever and attempts to resubmit any
> message that is submitted to it to the parent controller with some
> adjusted callbacks.  This does not play at all nicely with the fast
> path which now sets flags on the message indicating that it's being
> handled through the fast path, we see async messages flagged as being on
> the fast path.  Ideally the spi-mux code would duplicate the message but
> that's rather invasive and a bit fragile in that it relies on the mux
> knowing which fields in the message to copy.  Instead teach the core
> that there are controllers which can't cope with the fast path and have
> the mux flag itself as being such a controller, ensuring that messages
> going via the mux don't get partially handled via the fast path.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: mux: Fix mux interaction with fast path optimisations
      commit: b30f7c8eb0780e1479a9882526e838664271f4c9

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