linux-kernel - Re: [PATCH v2] ASoC: wm8960: Remove bitclk relax condition in wm8960_configure

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: <161669370550.41585.9109635585401644966.b4-ty@kernel.org>
Date:   Thu, 25 Mar 2021 17:37:03 +0000
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com, gustavoars@...nel.org,
        tiwai@...e.com, perex@...ex.cz,
        pierre-louis.bossart@...ux.intel.com, peter.ujfalusi@...com,
        Shengjiu Wang <shengjiu.wang@....com>,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        kuninori.morimoto.gx@...esas.com, lgirdwood@...il.com,
        patches@...nsource.cirrus.com, daniel.baluta@....com
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2] ASoC: wm8960: Remove bitclk relax condition in wm8960_configure_sysclk

On Wed, 3 Mar 2021 11:07:42 +0800, Shengjiu Wang wrote:
> The call sequence in wm8960_configure_clocking is
> 
>    ret = wm8960_configure_sysclk();
>    if (ret >= 0)
>         goto configure_clock;
> 
>    ....
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm8960: Remove bitclk relax condition in wm8960_configure_sysclk
      commit: 99067c07e8d877035f6249d194a317c78b7d052d

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