linux-kernel - Re: [RESEND PATH] ASoC: dmaengine_pcm: add peripheral configuration

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]

Date:   Fri, 05 Feb 2021 20:14:37 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lars@...afoo.de, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, tiwai@...e.com,
        Shengjiu Wang <shengjiu.wang@....com>, perex@...ex.cz
Subject: Re: [RESEND PATH] ASoC: dmaengine_pcm: add peripheral configuration

On Fri, 5 Feb 2021 15:26:25 +0800, Shengjiu Wang wrote:
> The commit e7bbb7acabf4 ("dmaengine: add peripheral configuration")
> adds peripheral configuration for dma_slave_config.
> 
> This configuration is useful for some audio peripherals, for
> example, the peripheral supports multi fifos, we can
> let the DMA know which fifos are selected. So also add
> this configuration for snd_dmaengine_dai_dma_data.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: dmaengine_pcm: add peripheral configuration
      commit: 500c9f8c58a7c8cd5d9c1483569c046cfcfc47a4

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