[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <160504428418.41991.4621142388350710965.b4-ty@kernel.org>
Date: Tue, 10 Nov 2020 21:38:09 +0000
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.com, pierre-louis.bossart@...ux.intel.com,
lgirdwood@...il.com, kuninori.morimoto.gx@...esas.com,
perex@...ex.cz, Sameer Pujar <spujar@...dia.com>
Cc: linux-tegra@...r.kernel.org, alsa-devel@...a-project.org,
thierry.reding@...il.com, jonathanh@...dia.com, sharadg@...dia.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/7] Audio Graph Updates
On Mon, 2 Nov 2020 20:40:07 +0530, Sameer Pujar wrote:
> This series is a prepraration for using generic graph driver for Tegra210
> audio. Tegra audio graph series will be sent in a separate series because
> it has some dependency over other series for documentation work. This
> series can focus on the generic ASoC driver updates. Below are the summary
> of changes done.
>
> * Support multiple instances of a component. For example there can be
> multiple I2S devices which can use the same component driver.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: soc-core: Fix component name_prefix parsing
commit: 3256ef984b016fc8491f34cad594168b4b500317
[2/7] ASoC: soc-pcm: Get all BEs along DAPM path
commit: aa293777bfeb75fb8872565ef99cc0e8b98b5c7d
[3/7] ASoC: audio-graph: Use of_node and DAI for DPCM DAI link names
commit: e6aeb375d25dba56c4089b1d6aa0a77fe218ef3b
[4/7] ASoC: audio-graph: Identify 'no_pcm' DAI links for DPCM
commit: c21cbb526c0a105d582299839a9c4244dd6bf38a
[5/7] ASoC: audio-graph: Support empty Codec endpoint
commit: 930dd47d74023e7c94a7c256279e12924c14475d
[6/7] ASoC: audio-graph: Expose new members for asoc_simple_priv
commit: d09c774f2f9ff25817866b70f1fb9603e5196971
[7/7] ASoC: audio-graph: Expose helpers from audio graph
commit: e32b100bc6ecbc390aae728fc7d2a3e247faa8a7
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
Powered by blists - more mailing lists