Message ID | 87o73mqj5b.wl-kuninori.morimoto.gx@renesas.com |
---|---|
Headers | show |
Series | ASoC: remove dpcm_xxx flags | expand |
On Tue, 15 Oct 2024 00:55:44 +0000, Kuninori Morimoto wrote: > 2 weeks past. This is v4 patch-set > > Now, we don't need to use dpcm_playback/capture flags for DPCM since v6.11, > and thus we can use playback/capture_only flags instead too for DPCM, > which is same as non-DPCM. > > Let's remove dpcm_playback/capture flags, and use playback/capture_only flags > instead. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: amd: remove dpcm_xxx flags commit: 12c61265e5b687b155d08e052c2b6d78eaee4849 [02/13] ASoC: fsl: remove dpcm_xxx flags commit: efa527f984a110944d9640b81ff94d0a5401b3fb [03/13] ASoC: sof: remove dpcm_xxx flags commit: 90bbbf612f9e5e4548b27b213b1866b4feb670bd [04/13] ASoC: intel: remove dpcm_xxx flags commit: d26aed5eba16bf5a4aa86bc717edf0b5ed192b93 [05/13] ASoC: samsung: remove dpcm_xxx flags commit: fa9c4b46fb76e2cb36bd8f94a096e61ebdb8b7f9 [06/13] ASoC: mediatek: remove dpcm_xxx flags commit: ec15e5043d0bedcb93a2653725fb50d5b358b06b [07/13] ASoC: soc-core: remove dpcm_xxx flags commit: b6b8caf6470b9793ae4b66a95c742a1c97ece748 [08/13] ASoC: soc-compress: remove dpcm_xxx flags commit: 0f77c88f0e3a3945c328bbb9a9e3c4b5826e8fe0 [09/13] ASoC: soc-topology: remove dpcm_xxx flags commit: 44b6f24018317f6096007d9d397e6f3dfb0131ae [10/13] ASoC: intel: boards: remove dpcm_xxx flags commit: ae0967da4bbfadc7156ba1deeb16fb31495ea359 [11/13] ASoC: soc-pcm: remove dpcm_xxx flags commit: c7ae6551533e7c7bf903a2d259044778f4b103ce [12/13] ASoC: doc: remove dpcm_xxx flags commit: 0e3dc8e4bd4a739401ada1541452fe1499254680 [13/13] ASoC: soc-pcm: merge DPCM and non-DPCM validation check commit: a6ff8572fd3fafe3f0f39e94ad8d4b6c88de7e03 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