linux-kernel - Re: [PATCH] ASoC: atmel-i2s: do not warn if muxclk is missing

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: <160442726962.14840.2168034632835702647.b4-ty@kernel.org>
Date:   Tue, 03 Nov 2020 18:14:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Codrin Ciubotariu <codrin.ciubotariu@...rochip.com>,
        alsa-devel@...a-project.org, linux-arm-kernel@...ts.infradead.org
Cc:     ludovic.desroches@...rochip.com, nicolas.ferre@...rochip.com,
        alexandre.belloni@...tlin.com, lgirdwood@...il.com
Subject: Re: [PATCH] ASoC: atmel-i2s: do not warn if muxclk is missing

On Tue, 3 Nov 2020 12:05:54 +0200, Codrin Ciubotariu wrote:
> Besides the fact that muxclk is optional, muxclk can be set using
> assigned-clocks, removing the need to set it in driver. The warning is
> thus unneeded, so we can transform it in a debug print, eventually to just
> reflect that muxclk was not set by the driver.

Applied to

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

Thanks!

[1/1] ASoC: atmel-i2s: do not warn if muxclk is missing
      commit: f4bf1f4d1385b7cb61a3fc811bb4912d49aa394a

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