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: <169238110424.55727.14056670602872102489.b4-ty@kernel.org>
Date:   Fri, 18 Aug 2023 18:51:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Alper Nebi Yasak <alpernebiyasak@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Vijendar Mukunda <Vijendar.Mukunda@....com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Venkata Prasad Potturu <venkataprasad.potturu@....com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: amd: acp: Add kcontrols and widgets per-codec in
 common code

On Fri, 18 Aug 2023 11:03:14 +0300, Alper Nebi Yasak wrote:
> Commit 7ac3404c2e21 ("ASoC: amd: acp: Map missing jack kcontrols") adds
> card kcontrols and DAPM widgets corresponding to jacks for Headphone and
> Headset Mic. But these were already being added in acp-legacy-mach.c and
> acp-sof-mach.c, so this causes a probe error:
> 
>   sof_mach rt5682s-hs-rt1019: control 2:0:0:Headphone Jack Switch:0 is already present
>   sof_mach rt5682s-hs-rt1019: ASoC: Failed to add Headphone Jack Switch: -16
>   sof_mach rt5682s-hs-rt1019: devm_snd_soc_register_card(sof-rt5682s-hs-rt1019) failed: -16
>   sof_mach: probe of rt5682s-hs-rt1019 failed with error -16
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: Add kcontrols and widgets per-codec in common code
      commit: 919a4a941863c539e982d34903e93d9777316f7d

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ