Re: Applied "ASoC: core: Don't schedule DAPM work if already in target state" to the spi tree

[Jon Hunter <jonathanh@xxxxxxxxxx>]

Hi Mark,

On 28/08/18 21:58, Mark Brown wrote:
> The patch
> 
>    ASoC: core: Don't schedule DAPM work if already in target state
> 
> has been applied to the spi tree at
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git 
> 
> 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.

Is the above tree correct? I would have expected this to go via your
sound tree. I have not seen in turn up in -next yet and so wanted to check.

Cheers
Jon

-- 
nvpublic