linux-kernel - Re: [PATCH 1/2] ASoC: sun8i-codec: Partial revert to fix clock specifiers

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 for Android: free password hash cracker in your pocket

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

Message-Id: <165520231251.3607327.1586830877046934824.b4-ty@kernel.org>
Date:   Tue, 14 Jun 2022 11:25:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com, samuel@...lland.org
Cc:     linux-mediatek@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
        patches@...nsource.cirrus.com, jernej.skrabec@...il.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        wens@...e.org, lgirdwood@...il.com, matthias.bgg@...il.com
Subject: Re: [PATCH 1/2] ASoC: sun8i-codec: Partial revert to fix clock specifiers

On Mon, 13 Jun 2022 17:15:51 +0100, Charles Keepax wrote:
> Recent updates accidentally updated the clock producer/consumer
> specifiers on this device as part of refactoring the CPU side of the DAI
> links. However, this device sits on the CODEC side and shouldn't have
> been updated. Partially revert the changes keeping the switch to the new
> clock terminology but going back to the CODEC defines.
> 
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: sun8i-codec: Partial revert to fix clock specifiers
      commit: beb89d1d49e9ae1188356d6e37581e5f0b5f62b4
[2/2] ASoC: mediatek: mt8186: Use new direct clock defines
      commit: 845a215558647acd4290dd773b9c0de62c123335

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