From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
Cc: yung-chuan.liao@linux.intel.com, lgirdwood@gmail.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
peter.ujfalusi@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ASoC: SOF: compress: Add support for timestamp on capture
Date: Wed, 31 Aug 2022 13:52:51 +0100 [thread overview]
Message-ID: <166195037191.99184.7695234970678699743.b4-ty@kernel.org> (raw)
In-Reply-To: <20220822101502.17644-1-laurentiu.mihalcea@nxp.com>
On Mon, 22 Aug 2022 13:15:00 +0300, Laurentiu Mihalcea wrote:
> The purpose of this patch series is to add support for
> timestamping on capture direction using the compress
> API.
>
> This is simply done by splitting sof_compr_copy into 2
> functions: sof_compr_copy_playback and sof_compr_copy_capture.
> Each of these functions handles one of the possible directions:
> capture or playback and is called in sof_compr_copy based on
> the stream's direction.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: SOF: compress: Move sof_compr_copy functionality
commit: 272ff8828f35658aace17e3227624fbbd68a6bcf
[2/2] ASoC: SOF: compress: Add copy function for capture case
commit: 1a01e19278022cd2f7daa7a065ed47c5022dbad9
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:[~2022-08-31 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 10:15 Laurentiu Mihalcea
2022-08-22 10:15 ` [PATCH 1/2] ASoC: SOF: compress: Move sof_compr_copy functionality Laurentiu Mihalcea
2022-08-22 10:15 ` [PATCH 2/2] ASoC: SOF: compress: Add copy function for capture case Laurentiu Mihalcea
2022-08-31 12:52 ` 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=166195037191.99184.7695234970678699743.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=laurentiu.mihalcea@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.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®