linux-kernel - Re: [PATCH 0/3] ASoC: fsl_micfil: fix and improvement

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: <172780520382.2298697.5976871562900019910.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 18:53:23 +0100
From: Mark Brown <broonie@...nel.org>
To: shengjiu.wang@...il.com, Xiubo.Lee@...il.com, festevam@...il.com, 
 nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 alsa-devel@...a-project.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH 0/3] ASoC: fsl_micfil: fix and improvement

On Fri, 27 Sep 2024 16:00:28 +0800, Shengjiu Wang wrote:
> Fix the usage of regmap_write_bits().
> Move mclk clock enablement to late stage.
> Enable the micfil error interrupt.
> 
> Shengjiu Wang (3):
>   ASoC: fsl_micfil: fix regmap_write_bits usage
>   ASoC: fsl_micfil: Add mclk enable flag
>   ASoC: fsl_micfil: Enable micfil error interrupt
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: fsl_micfil: fix regmap_write_bits usage
      commit: 06df673d20230afb0e383e39235a4fa8b9a62464
[2/3] ASoC: fsl_micfil: Add mclk enable flag
      commit: b47024dc624bcffb89d238f4a5b490363cea2a1e
[3/3] ASoC: fsl_micfil: Enable micfil error interrupt
      commit: cc3ae21f360bfa375fc3539e24e7adb0e643a9d4

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