Skip to contentSkip to conversation

ASoC: codecs: jz4725b: Fix spelling mistake "Sourc" -> "Source", "Routee" -> "Route"

PATCH In review Colin Ian King 4 participants 8 messages Oct 19, 2022

Subsystems (5)
Sound Kernel janitors MIPS ASoC +1 more subsystems
lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 ASoC: codecs: jz4725b: Fix spelling mistake "Sourc" -> "Source", "Routee" -> "Route"

There are two spelling mistakes in codec routing description. Fix it.

---
V2: Fix "Routee" -> "Route" too

---
 sound/soc/codecs/jz4725b.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/jz4725b.c +1 -1
index 685ba1d3a644..64b14b1c74b9 100644
@@ -359,7 +359,7 @@ static const struct snd_soc_dapm_route jz4725b_codec_dapm_routes[] = {
 
 	{"Mixer to ADC", NULL, "Mixer"},
 	{"ADC Source Capture Route", "Mixer", "Mixer to ADC"},
-	{"ADC Sourc Capture Routee", "Line In", "Line In"},
+	{"ADC Source Capture Route", "Line In", "Line In"},
 	{"ADC Source Capture Route", "Mic 1", "Mic 1"},
 	{"ADC Source Capture Route", "Mic 2", "Mic 2"},
 	{"ADC", NULL, "ADC Source Capture Route"},
Signature · 1 line
2.37.3
maintainer Acked-by on v2 1/1
#2 lore raw
In reply to Colin Ian King

Hi Colin,

Quoted 3 lines · Colin Ian King

There are two spelling mistakes in codec routing description. Fix it.

Cheers,
-Paul

Quoted 23 lines

---
V2: Fix "Routee" -> "Route" too

---
 sound/soc/codecs/jz4725b.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/jz4725b.c +1 -1
index 685ba1d3a644..64b14b1c74b9 100644
@@ -359,7 +359,7 @@ static const struct snd_soc_dapm_route 
 jz4725b_codec_dapm_routes[] = {
 
 	{"Mixer to ADC", NULL, "Mixer"},
 	{"ADC Source Capture Route", "Mixer", "Mixer to ADC"},
-	{"ADC Sourc Capture Routee", "Line In", "Line In"},
+	{"ADC Source Capture Route", "Line In", "Line In"},
 	{"ADC Source Capture Route", "Mic 1", "Mic 1"},
 	{"ADC Source Capture Route", "Mic 2", "Mic 2"},

{"ADC", NULL, "ADC Source Capture Route"},
--
2.37.3

maintainer
#3 lore raw
In reply to Colin Ian King
Quoted 1 line · Colin Ian King

There are two spelling mistakes in codec routing description. Fix it.

Bit disappionting that people didn't notice the errors during boot there...

maintainer
#4 lore raw

Hi Mark,

Quoted 6 lines · Mark Brown
Quoted 2 lines · Colin Ian King

There are two spelling mistakes in codec routing description. Fix
it.

Bit disappionting that people didn't notice the errors during boot there...

Well that's on you. You merged the patchset before anybody could review.

-Paul

#5 lore raw
Quoted 4 lines · Paul Cercueil

Hi Mark,

Quoted 1 line · Mark Brown

On Wed, Oct 19, 2022 at 08:16:39AM +0100, Colin Ian King wrote:

Quoted 10 lines
Quoted 4 lines
Quoted 1 line

 There are two spelling mistakes in codec routing description. Fix it.

Bit disappionting that people didn't notice the errors during boot there...

Well that's on you. You merged the patchset before anybody could review.

-Paul

Fortunately I spell check linux-next daily to catch these typos.

Colin

maintainer
#6 lore raw
In reply to Paul Cercueil
Quoted 10 lines · Paul Cercueil

Le mer., oct. 19 2022 at 13:10:49 +0100, Mark Brown <[email protected]> a

Quoted 7 lines · Colin Ian King
Quoted 3 lines

There are two spelling mistakes in codec routing description. Fix
it.

Bit disappionting that people didn't notice the errors during boot there...

Well that's on you. You merged the patchset before anybody could review.

That includes whoever wrote the code in the first place, and I do note that I applied version 3 of the series.

maintainer
#7 lore raw
In reply to Colin Ian King
Quoted 3 lines · Colin Ian King

There are two spelling mistakes in codec routing description. Fix it.

Applied to

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

Thanks!

[1/1] ASoC: codecs: jz4725b: Fix spelling mistake "Sourc" -> "Source", "Routee" -> "Route"

      commit: df496157a5afa1b6d1f4c46ad6549c2c346d1e59

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