linux-kernel - Re: [PATCH] ASoC: amd: Kconfig: Select fch clock support with machine driver

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: <163397094549.6567.3180566951499093730.b4-ty@kernel.org>
Date:   Mon, 11 Oct 2021 18:01:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Vijendar Mukunda <vijendar.mukunda@....com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Basavaraj.Hiregoudar@....com,
        open list <linux-kernel@...r.kernel.org>,
        Alexander.Deucher@....com, Vijendar.Mukunda@....com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Sunil-kumar.Dommati@....com
Subject: Re: [PATCH] ASoC: amd: Kconfig: Select fch clock support with machine driver

On Mon, 11 Oct 2021 11:23:53 +0530, Ajit Kumar Pandey wrote:
> We are using fch clock controller as parent mclk source for rt5682
> codec. Add config to enable clock framework support for 48MHz fixed
> clock when machine driver config is selected.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: Kconfig: Select fch clock support with machine driver
      commit: 281ddf62f551321982c7d6f525a83a3b3c1d5eae

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