linux-kernel - Re: [PATCH] ASoC: es8328: Remove duplicate DAPM routes

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: <176770206664.32636.14212285684486375827.b4-ty@kernel.org>
Date: Tue, 06 Jan 2026 12:21:06 +0000
From: Mark Brown <broonie@...nel.org>
To: Hsieh Hung-En <hungen3108@...il.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: es8328: Remove duplicate DAPM routes

On Wed, 31 Dec 2025 16:45:54 +0800, Hsieh Hung-En wrote:
> The DAPM routes for "Left Line Mux" and "Right Line Mux" are defined
> twice in es8328_dapm_routes[]. The redundant entries appear after
> the "Mic Bias" route and duplicate the definitions found earlier in
> the array.
> 
> Remove the duplicate entries to clean up the code.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: es8328: Remove duplicate DAPM routes
      commit: 52ddc0106c77ff0eacf07b309833ae6e6a4e8587

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