linux-kernel - Re: [PATCH 0/2] ASoC: SOF: compress: Add support for timestamp on capture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166195037191.99184.7695234970678699743.b4-ty@kernel.org>
Date:   Wed, 31 Aug 2022 13:52:51 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Laurentiu Mihalcea <laurentiu.mihalcea@....com>
Cc:     yung-chuan.liao@...ux.intel.com, lgirdwood@...il.com,
        ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
        peter.ujfalusi@...ux.intel.com,
        pierre-louis.bossart@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: SOF: compress: Add support for timestamp on capture

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