linux-kernel - Re: [PATCH v2] ASoC: Revert "ASoC: mediatek: Check for error clk pointer"

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: <164433287142.2964899.6109148874743045900.b4-ty@kernel.org>
Date:   Tue, 08 Feb 2022 15:07:51 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Guenter Roeck <linux@...ck-us.net>,
        Matthias Brugger <matthias.bgg@...il.com>
Cc:     Frank Wunderlich <frank-w@...lic-files.de>,
        linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org,
        Kevin Hilman <khilman@...libre.com>,
        Daniel Golle <daniel@...rotopia.org>,
        linux-kernel@...r.kernel.org,
        James Liao <jamesjj.liao@...iatek.com>,
        Jiasheng Jiang <jiasheng@...as.ac.cn>
Subject: Re: [PATCH v2] ASoC: Revert "ASoC: mediatek: Check for error clk pointer"

On Mon, 7 Feb 2022 08:09:23 -0800, Guenter Roeck wrote:
> This reverts commit 9de2b9286a6d ("ASoC: mediatek: Check for error clk
> pointer").
> 
> With this patch in the tree, Chromebooks running the affected hardware
> no longer boot. Bisect points to this patch, and reverting it fixes
> the problem.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Revert "ASoC: mediatek: Check for error clk pointer"
      commit: 946eb87114af37c9c13c618a7c1cdaca936905fa

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