linux-kernel - Re: [PATCH -next] ASoC: codecs: Remove unneeded semicolon

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: <170618995429.31781.12764498423630220145.b4-ty@kernel.org>
Date: Thu, 25 Jan 2024 13:39:14 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 Yang Li <yang.lee@...ux.alibaba.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] ASoC: codecs: Remove unneeded semicolon

On Wed, 24 Jan 2024 08:44:25 +0800, Yang Li wrote:
> In the wcd939x codec driver, there are two instances where semicolons
> are used after closing braces of a switch-case statement. These
> semicolons are not required and do not adhere to the coding style
> guidelines.
> 
> This patch removes the unnecessary semicolons at the end of the
> switch-case statements which cleans up the code and ensures consistency
> with the rest of the kernel coding style.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: Remove unneeded semicolon
      commit: e7214441ca1562fbfb002200f46d7f83bbc2e621

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