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  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:   Thu, 22 Jul 2021 18:10:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc:     Mark Brown <broonie@...nel.org>, Basavaraj.Hiregoudar@....com,
        Sunil-kumar.Dommati@....com, amistry@...gle.com,
        Alexander.Deucher@....com, Liam Girdwood <lgirdwood@...il.com>,
        nartemiev@...gle.com,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        open list <linux-kernel@...r.kernel.org>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Chuhong Yuan <hslester96@...il.com>
Subject: Re: [PATCH] ASoC: amd: enable stop_dma_first flag for cz_dai_7219_98357 dai link

On Thu, 22 Jul 2021 18:33:15 +0530, Vijendar Mukunda wrote:
> DMA driver stop sequence should be invoked first before invoking I2S
> controller driver stop sequence for Stoneyridge platform.
> 
> Enable stop_dma_first flag for cz_dai_7219_98357 dai link structure.

Applied to

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

Thanks!

[1/1] ASoC: amd: enable stop_dma_first flag for cz_dai_7219_98357 dai link
      commit: 5434d0dc56bce4510109a431a7eb71ec5131ef0f

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

Powered by blists - more mailing lists