[PATCH -next] ASoC: Remove unneeded semicolon

Yang Li posted 1 patch 1 year, 5 months ago
sound/soc/codecs/ak4619.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH -next] ASoC: Remove unneeded semicolon
Posted by Yang Li 1 year, 5 months ago
./sound/soc/codecs/ak4619.c:757:2-3: Unneeded semicolon

Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9442
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
---
 sound/soc/codecs/ak4619.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/ak4619.c b/sound/soc/codecs/ak4619.c
index cbe27abe1f50..8f2442482f72 100644
--- a/sound/soc/codecs/ak4619.c
+++ b/sound/soc/codecs/ak4619.c
@@ -754,7 +754,7 @@ static void ak4619_hw_constraints(struct ak4619_priv *ak4619,
 		default:
 			break;
 		}
-	};
+	}
 
 	constraint->list	= ak4619_sr;
 	constraint->mask	= ak4619_rate_mask;
-- 
2.20.1.7.g153144c
Re: [PATCH -next] ASoC: Remove unneeded semicolon
Posted by Mark Brown 1 year, 5 months ago
On Fri, 28 Jun 2024 13:24:06 +0800, Yang Li wrote:
> ./sound/soc/codecs/ak4619.c:757:2-3: Unneeded semicolon
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: Remove unneeded semicolon
      commit: 061505a1a61169bd25dd908f95ba22f33dffdd69

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