On Fri, 3 Jun 2022 16:05:09 +0200, Uwe Kleine-König wrote: > From: Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> > > Hello, > > I intended to send this after -rc1 was cut, but found a few spare > minutes to prepare this series. All four patches were sent already > before based on v5.18, but there were some conflicting changes added in > the merge window. This series contains the four patches on top of > current linus/master and so bases on a tree including the conflicting > changes. Expecting no more sound changes in this merge window, this > should apply cleanly on top of -rc1. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/4] ASoC: ak4642: Drop no-op remove function commit: 60391d788a221f1866492a71929483790b772676 [2/4] ASoC: da7219: Drop no-op remove function commit: 8a291eebeb633316edad2e80537a3c7df83ee8dc [3/4] ASoC: lm49453: Drop no-op remove function commit: 3cce931a5e4487f7339be559e2ea032478be021a [4/4] ASoC: da732x: Drop no-op remove function commit: fb68cb963bb78380166a98beea593d20b956e4c3 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
