ASoC: Intel: remove unneeded semicolon
Subsystems (3)
PATCH 1/1 ASoC: Intel: remove unneeded semicolon
From: Tom Rix <[email protected]>
A semicolon is not needed after a switch statement.
--- sound/soc/intel/atom/sst/sst.c | 2 +- sound/soc/intel/catpt/loader.c | 2 +- sound/soc/intel/catpt/pcm.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-)
sound/soc/intel/atom/sst/sst.c +1 -1
@@ -186,7 +186,7 @@ int sst_driver_ops(struct intel_sst_drv *sst)"SST Driver capabilities missing for dev_id: %x" , sst->dev_id);return -EINVAL ; - }; + } }void sst_process_pending_msg (struct work_struct *work)
sound/soc/intel/catpt/loader.c +1 -1
@@ -304,7 +304,7 @@ static int catpt_load_block(struct catpt_dev *cdev,default : sram = &cdev->dram;break ; - }; + } dst_addr = sram->start + blk->ram_offset;if (alloc) {
sound/soc/intel/catpt/pcm.c +2 -2
@@ -92,7 +92,7 @@ catpt_get_stream_template(struct snd_pcm_substream *substream)break ;default :break ; - }; + }return catpt_topology[type]; }
@@ -419,7 +419,7 @@ static int catpt_dai_apply_usettings(struct snd_soc_dai *dai,break ;default :return 0 ; - }; + }list_for_each_entry (pos, &component->card->snd_card->controls, list) { if (pos->private_data == component &&
Signature · 1 line
2.18.1
Quoted 6 lines · On 2020-11-01 6:19 PM, [email protected] wrote:
From: Tom Rix <[email protected]>
A semicolon is not needed after a switch statement.
Signed-off-by Tom Rix <[email protected]>---
Thanks for this update, Tom.
Regards,
Czarek
Mark Brown
maintainerQuoted 1 line · On Sun, 1 Nov 2020 09:19:43 -0800, [email protected] wrote:
A semicolon is not needed after a switch statement.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Intel: remove unneeded semicolon
commit: c1af06a28a0176ceb1fc71408b32aabf53db4470
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