On Wed, 27 Oct 2021 10:18:14 +0800, Bard Liao wrote: > This series provides a way to use constant dailink numbers for different > devices. So that we don't need to renumber them in topologies. > Some patches with different purpose are sent together in this series > since they are dependent. > > Bard Liao (8): > ASoC: intel: sof_sdw: return the original error number > ASoC: intel: sof_sdw: rename be_index/link_id to link_index > ASoC: intel: sof_sdw: Use a fixed DAI link id for AMP > ASoC: intel: sof_sdw: move DMIC link id overwrite to > create_sdw_dailink > ASoC: intel: sof_sdw: remove SOF_RT715_DAI_ID_FIX quirk > ASoC: intel: sof_sdw: remove sof_sdw_mic_codec_mockup_init > ASoC: intel: sof_sdw: remove get_next_be_id > ASoC: intel: sof_sdw: add link adr order check > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/10] ASoC: intel: sof_sdw: return the original error number commit: dd31ddd81904070d0a9cafd5499d3210a322f8af [02/10] ASoC: Intel: sof_sdw: fix jack detection on HP Spectre x360 convertible commit: 0527b19fa4f390a6054612e1fa1dd4f8efc96739 [03/10] ASoC: Intel: sof_sdw: add SKU for Dell Latitude 9520 commit: 1071f2415b6b4ee653869acabfb26de1a27da9cd [04/10] ASoC: intel: sof_sdw: rename be_index/link_id to link_index commit: b63137cf5167b73d9d68a2334b835996bfc3b941 [05/10] ASoC: intel: sof_sdw: Use a fixed DAI link id for AMP commit: d471c034f83201f84330e9ed46ad5139d32e77ce [06/10] ASoC: intel: sof_sdw: move DMIC link id overwrite to create_sdw_dailink commit: bf605cb042307d162fbcb094738bab5d767f1261 [07/10] ASoC: intel: sof_sdw: remove SOF_RT715_DAI_ID_FIX quirk commit: f8f8312263e2d0c38dd0330a4503dcdcc94d0cd5 [08/10] ASoC: intel: sof_sdw: remove sof_sdw_mic_codec_mockup_init commit: bd98394a811c7dc39bcd189cf5f33925f0c30ae2 [09/10] ASoC: intel: sof_sdw: remove get_next_be_id commit: 4ed65d6ead29a992c4803e1138a6042caa6ec2a3 [10/10] ASoC: intel: sof_sdw: add link adr order check commit: 296c789ce1e501be8b46ebb24da4ba53063cc10a 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
