linux-kernel - Re: [PATCH] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id

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: <164150089750.2243486.8547152917333843393.b4-ty@kernel.org>
Date:   Thu, 06 Jan 2022 20:28:17 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        alsa-devel@...a-project.org
Cc:     Jaroslav Kysela <perex@...ex.cz>,
        Liam Girdwood <lgirdwood@...il.com>,
        open list <linux-kernel@...r.kernel.org>,
        Basavaraj.Hiregoudar@....com, Takashi Iwai <tiwai@...e.com>,
        Alexander.Deucher@....com, Sunil-kumar.Dommati@....com,
        V sujith kumar Reddy <vsujithkumar.reddy@....com>,
        Vijendar.Mukunda@....com
Subject: Re: [PATCH] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id

On Thu, 6 Jan 2022 20:35:21 +0530, Ajit Kumar Pandey wrote:
> RT1019 components was initially registered with i2c1 and i2c2 but
> now changed to i2c0 and i2c1 in most of our AMD platforms. Change
> default rt1019 components to 10EC1019:00 and 10EC1019:01 which is
> aligned with most of AMD machines.
> 
> Any exception to rt1019 device ids in near future board design can
> be handled using dmi based quirk for that machine.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
      commit: 7112550890d7e415188a3351ec0a140be60f6deb

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