From: Mark Brown <broonie@kernel.org>
To: Kirill Marinushkin <kmarinushkin@birdec.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Takashi Iwai <tiwai@suse.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-kernel@vger.kernel.org, Matthias Reichl <hias@horus.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v3 0/4] ASoC: pcm512x: Patch series to set fmt from `set_fmt()`
Date: Mon, 16 Nov 2020 23:32:56 +0000 [thread overview]
Message-ID: <160556956526.29683.6599781233206972727.b4-ty@kernel.org> (raw)
In-Reply-To: <20201115122306.18164-1-kmarinushkin@birdec.com>
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
prev parent reply other threads:[~2020-11-16 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 12:23 [PATCH v3 0/4] ASoC: pcm512x: Patch series to set fmt from `set_fmt()` Kirill Marinushkin
2020-11-15 12:23 ` [PATCH v3 1/4] ASoC: pcm512x: Fix not setting word length if DAIFMT_CBS_CFS Kirill Marinushkin
2020-11-15 12:23 ` [PATCH v3 2/4] ASoC: pcm512x: Rearrange operations in `hw_params()` Kirill Marinushkin
2020-11-15 12:23 ` [PATCH v3 3/4] ASoC: pcm512x: Move format check into `set_fmt()` Kirill Marinushkin
2020-11-15 12:23 ` [PATCH v3 4/4] ASoC: pcm512x: Add support for more data formats Kirill Marinushkin
2020-11-16 12:18 ` [PATCH v3 0/4] ASoC: pcm512x: Patch series to set fmt from `set_fmt()` Peter Ujfalusi
2020-11-16 23:32 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160556956526.29683.6599781233206972727.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hias@horus.com \
--cc=kmarinushkin@birdec.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).