On Sun, 4 Oct 2020 12:01:15 +0200, Cezary Rojewski wrote: > Follow up to catpt series as mentioned in: > [PATCH v10 00/14] ASoC: Intel: Catpt - Lynx and Wildcat point > https://www.spinics.net/lists/alsa-devel/msg116440.html > > As catpt is a direct replacement to sound/soc/intel/haswell, it leaves a > lot of code redudant. The second legacy solution - baytrail - is > deprecated for a long time by sound/soc/intel/atom with SOF flavor > available too. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: Intel: Remove haswell solution commit: ca756120d4bcf28dfde5e3df8882153303d4010f [02/13] ASoC: Intel: Remove max98090 support for baytrail solution commit: 5f3941b63c25d8123ebe4406a714c603525b1b90 [03/13] ASoC: Intel: Remove rt5640 support for baytrail solution commit: 3056cb0082feccee9a0012440ee5e4ca6a6e80ac [04/13] ASoC: Intel: Remove baytrail solution commit: 07833cd0569bb73cc9f82814cdab921abb3dfb4a [05/13] ASoC: Intel: Remove SST ACPI component commit: 05668be1b3644f9bd25b22f62e79ad7a5adbd3e2 [06/13] ASoC: Intel: Remove SST firmware components commit: fb94b7b11c6a20b786c6a8aec3d701ced8854419 [07/13] ASoC: Intel: Skylake: Unassign ram_read and read_write ops commit: a4bebce26d560a4a1dff557ad7822bab90dd1c3f [08/13] ASoC: Intel: Remove unused DSP operations commit: 37465972015cf7aeb586a9245da2a87d3b531959 [09/13] ASoC: Intel: Remove unused DSP interface fields commit: b4e60807182a243d9dfe985e9e13d295f5868f81 [10/13] ASoC: Intel: Remove SST-legacy specific constants commit: 7d07f9c1ba0e670d1a967f16eda53e5c87411753 [11/13] ASoC: Intel: Make atom components independent of sst-dsp commit: b972153d6c53a89dc92d991c466a6b4800a9c91f [12/13] ASoC: Intel: Remove sst_pdata structure commit: 720811f0e4ac5a31d38aaee20905692dd7150997 [13/13] ASoC: Intel: Remove sst_dsp_get_thread_context commit: eb062e47f7c8cc28f19ba8f897481c22d13db1ec 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
