linux-kernel - Re: [PATCH V2][next] ASoC: rt722-sdca: Remove logically deadcode in rt722-sdca.c

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: <172866019117.3915434.7963769393055061429.b4-ty@kernel.org>
Date: Fri, 11 Oct 2024 16:23:11 +0100
From: Mark Brown <broonie@...nel.org>
To: oder_chiou@...ltek.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, "Everest K.C." <everestkc@...restkc.com.np>
Cc: skhan@...uxfoundation.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2][next] ASoC: rt722-sdca: Remove logically deadcode
 in rt722-sdca.c

On Thu, 10 Oct 2024 11:57:54 -0600, Everest K.C. wrote:
> As the same condition was checked in inner and outer if statements.
> The code never reaches the inner else statement.
> Fix this by removing the logically dead inner else statement.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt722-sdca: Remove logically deadcode in rt722-sdca.c
      commit: 22206e569fb54bf9c95db9a0138a7485ba9e13bc

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