[Sound-open-firmware] [PATCH 0/8] use semicolons rather than commas to separate statements

[Mark Brown]

On Sun, 11 Oct 2020 11:19:31 +0200, Julia Lawall wrote:
> These patches replace commas by semicolons.  This was done using the
> Coccinelle semantic patch (http://coccinelle.lip6.fr/) shown below.
> 
> This semantic patch ensures that commas inside for loop headers will not be
> transformed.  It also doesn't touch macro definitions.
> 
> Coccinelle ensures that braces are added as needed when a single-statement
> branch turns into a multi-statement one.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: wm8350: use semicolons rather than commas to separate statements
      commit: 2db5fa77cd7ea4bd18c7e1afb49417debc9f498a
[2/6] ASoC: Intel: bytcr_rt5651: use semicolons rather than commas to separate statements
      commit: edc3f5b43a4446c84069e59df7e48663ec28579d
[3/6] ASoC: SOF: Intel: hda: use semicolons rather than commas to separate statements
      commit: bed5ed644c741fd69a19a3cb811b5c1da1d50755
[4/6] ASoC: samsung: snow: use semicolons rather than commas to separate statements
      commit: 40faaca03bf7d7ca1480677f0c8c543016cf426d
[5/6] ASoC: madera: use semicolons rather than commas to separate statements
      commit: 94fa760d01c21350261388f404e167d5cb752573
[6/6] ASoC: dapm: use semicolons rather than commas to separate statements
      commit: a1344daeab95b93dd1d19fcfbc7dbaf2a4735129

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