From: Mark Brown <broonie@kernel.org>
To: nicoleotsuka@gmail.com, Shengjiu Wang <shengjiu.wang@nxp.com>,
timur@kernel.org, tiwai@suse.com, festevam@gmail.com,
lars@metafoo.de, Xiubo.Lee@gmail.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
perex@perex.cz, lgirdwood@gmail.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v3 0/4] Reuse the dma channel if available in Back-End
Date: Fri, 12 Jun 2020 14:59:01 +0100 [thread overview]
Message-ID: <159197034097.50978.12090792972224185067.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1591947428.git.shengjiu.wang@nxp.com>
On Fri, 12 Jun 2020 15:37:47 +0800, Shengjiu Wang wrote:
> Reuse the dma channel if available in Back-End
>
> Shengjiu Wang (4):
> ASoC: soc-card: export snd_soc_lookup_component_nolocked
> ASoC: dmaengine_pcm: export soc_component_to_pcm
> ASoC: fsl_asrc_dma: Reuse the dma channel if available in Back-End
> ASoC: fsl_asrc_dma: Fix data copying speed issue with EDMA
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: soc-card: export snd_soc_lookup_component_nolocked
commit: 6fbea6b6a838f9aa941fe53a3637fd8d8aab1eba
[2/4] ASoC: dmaengine_pcm: export soc_component_to_pcm
commit: a9a21e1eafc94b79502cab8272b392f7f63ef7bb
[3/4] ASoC: fsl_asrc_dma: Reuse the dma channel if available in Back-End
commit: 706e2c8811585f42612b6cff218ab3adbe63a4ee
[4/4] ASoC: fsl_asrc_dma: Fix data copying speed issue with EDMA
commit: b287a6d9723c601dd947f1c27d4cc0192e384a5a
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-06-12 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 7:37 Shengjiu Wang
2020-06-12 7:37 ` [RFC PATCH v3 1/4] ASoC: soc-card: export snd_soc_lookup_component_nolocked Shengjiu Wang
2020-06-12 8:00 ` Nicolin Chen
2020-06-12 7:37 ` [RFC PATCH v3 2/4] ASoC: dmaengine_pcm: export soc_component_to_pcm Shengjiu Wang
2020-06-12 8:01 ` Nicolin Chen
2020-06-12 7:37 ` [RFC PATCH v3 3/4] ASoC: fsl_asrc_dma: Reuse the dma channel if available in Back-End Shengjiu Wang
2020-06-12 8:08 ` Nicolin Chen
2020-06-12 7:37 ` [RFC PATCH v3 4/4] ASoC: fsl_asrc_dma: Fix data copying speed issue with EDMA Shengjiu Wang
2020-06-12 8:10 ` Nicolin Chen
2020-06-12 13:59 ` 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=159197034097.50978.12090792972224185067.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@nxp.com \
--cc=timur@kernel.org \
--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
all inboxes | Powered by JetHome®