From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2 0/8] ASoC: add snd_compress_ops and replace
Date: Tue, 21 Apr 2020 19:22:35 +0100 [thread overview]
Message-ID: <158749333763.13706.276874589638427328.b4-ty@kernel.org> (raw)
In-Reply-To: <87wo6avdq1.wl-kuninori.morimoto.gx@renesas.com>
On 20 Apr 2020 16:05:42 +0900, Kuninori Morimoto wrote:
>
> Hi Mark
>
> Current snd_soc_component_driver has compr_ops,
> but it is created for ALSA, not for ALSA SoC.
> This means it doesn't know the callback is for which component,
> thus, each callback needs to get component via lookup function.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.8
Thanks!
[1/8] ASoC: soc-compress: add snd_compress_ops
commit: c6cb522c1461eee41f086839bd3c9cb622cd26ca
[2/8] ASoC: codec: wm_adsp: use snd_compress_ops
commit: 3a5ccf25ee184510980a2c48606f7a004a2c844b
[3/8] ASoC: uniphier: use snd_compress_ops
commit: 171d1785c703e2f3713a877881412145f6ce98ca
[4/8] ASoC: qcom: q6sp6: use snd_compress_ops
commit: 849db80ef0ba272dbffe2ca5de6f3ffa09b5a76c
[5/8] ASoC: intel: atom: use snd_compress_ops
commit: c60e4459c42de356b5cc49830fc08e5fd372a8cd
[6/8] ASoC: sof: use snd_compress_ops
commit: 39118ce50b85496c0d78614474009fb8cbebb857
[7/8] ASoC: sprd: use snd_compress_ops
commit: 27ecad217c1437761cb4a9e1409d08bd287c18ed
[8/8] ASoC: soc-compress: remove snd_compr_ops
commit: e7cbe528391ab6660f747095efb6ee1542e4f205
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-04-21 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:05 [PATCH v2 0/8] ASoC: add snd_compress_ops and replace Kuninori Morimoto
2020-04-20 7:07 ` [PATCH v2 1/8] ASoC: soc-compress: add snd_compress_ops Kuninori Morimoto
2020-04-21 12:49 ` Charles Keepax
2020-04-20 7:08 ` [PATCH v2 2/8] ASoC: codec: wm_adsp: use snd_compress_ops Kuninori Morimoto
2020-04-21 12:51 ` Charles Keepax
2020-04-20 7:08 ` [PATCH v2 3/8] ASoC: uniphier: " Kuninori Morimoto
2020-04-20 7:08 ` [PATCH v2 4/8] ASoC: qcom: q6sp6: " Kuninori Morimoto
2020-04-20 7:09 ` [PATCH v2 5/8] ASoC: intel: atom: " Kuninori Morimoto
2020-04-20 7:09 ` [PATCH v2 6/8] ASoC: sof: " Kuninori Morimoto
2020-04-20 7:10 ` [PATCH v2 7/8] ASoC: sprd: " Kuninori Morimoto
2020-04-20 7:10 ` [PATCH v2 8/8] ASoC: soc-compress: remove snd_compr_ops Kuninori Morimoto
2020-04-21 12:51 ` Charles Keepax
2020-04-20 21:43 ` [PATCH v2 0/8] ASoC: add snd_compress_ops and replace Ranjani Sridharan
2020-04-21 18:22 ` 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=158749333763.13706.276874589638427328.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.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