[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <160556956526.29683.6599781233206972727.b4-ty@kernel.org>
Date: Mon, 16 Nov 2020 23:32:56 +0000
From: Mark Brown <broonie@...nel.org>
To: Kirill Marinushkin <kmarinushkin@...dec.com>,
Liam Girdwood <lgirdwood@...il.com>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Takashi Iwai <tiwai@...e.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
linux-kernel@...r.kernel.org, Matthias Reichl <hias@...us.com>,
alsa-devel@...a-project.org
Subject: Re: [PATCH v3 0/4] ASoC: pcm512x: Patch series to set fmt from `set_fmt()`
On Sun, 15 Nov 2020 13:23:02 +0100, Kirill Marinushkin wrote:
> Set format from `set_fmt()` func instead of `hw_params()`, plus supportive
> commits
>
> Kirill Marinushkin (4):
> ASoC: pcm512x: Fix not setting word length if DAIFMT_CBS_CFS
> ASoC: pcm512x: Rearrange operations in `hw_params()`
> ASoC: pcm512x: Move format check into `set_fmt()`
> ASoC: pcm512x: Add support for more data formats
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: pcm512x: Fix not setting word length if DAIFMT_CBS_CFS
commit: 6feaaa7c19bde25595e03bf883953f85711e4ac8
[2/4] ASoC: pcm512x: Rearrange operations in `hw_params()`
commit: 798714b6121d833c8abe4161761a94fdd1e73a90
[3/4] ASoC: pcm512x: Move format check into `set_fmt()`
commit: 26b97d95a05d0346e1ad6096deedac3f24a4607b
[4/4] ASoC: pcm512x: Add support for more data formats
commit: 25d27c4f68d2040c4772d586be3e02ee99eb71af
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