ASoC: fix typos in comments
Subsystems (5)
cover ASoC: fix typos in comments
This corrects 3 misspellings in comments. Each is a separate patch so that any one of them can be dropped without touching the rest.
Nothing outside comments changes. Every touched C file was checked by dropping its comments, replacing each string literal with a placeholder and collapsing whitespace; what remained was identical before and after, so the compiled code cannot differ.
The mistakes were found with scripts/checkpatch.pl against the list in scripts/spelling.txt. The scanning, the edits and the changelogs were produced with Cursor running the claude-opus-5 model, from a request to find and fix spelling mistakes across the tree, and every correction was then re-checked by the comparison described above. Words that name an identifier were left alone deliberately, even when they read as typos, because correcting the prose would make the comment disagree with the code it describes.
Tested by building x86_64 defconfig at v7.3-rc1-269-gbc35965f6940, which is clean. Nothing else was built, so any patch touching code that x86_64 defconfig does not compile has been read but not compiled.
Hemanth Selam (3):
ASoC: codecs: fix typos in comments
firmware: cirrus: fix typo "upto" in comment
mfd: fix typo "convertor" in comment
drivers/firmware/cirrus/cs_dsp.c | 2 +- drivers/mfd/wm831x-auxadc.c | 2 +- sound/soc/codecs/wm8962.c | 4 ++-- sound/soc/codecs/wm8996.c | 2 +- sound/soc/codecs/wm_hubs.c | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-)
Signature · 1 line
2.48.1
PATCH 1/3 ASoC: codecs: fix typos in comments
Fix typos in comments, reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes.
--- sound/soc/codecs/wm8962.c | 4 ++-- sound/soc/codecs/wm8996.c | 2 +- sound/soc/codecs/wm_hubs.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
sound/soc/codecs/wm8962.c +2 -2
@@ -3430,7 +3430,7 @@ static int wm8962_gpio_request(struct gpio_chip *chip, unsigned offset)/* The WM8962 GPIOs aren't linearly numbered. For simplicity * we export linear numbers and error out if the unsupported -* ones are requsted. +* ones are requested. */ switch (offset +1 ) {case 2 :
@@ -3813,7 +3813,7 @@ static int wm8962_i2c_probe(struct i2c_client *i2c)regmap_update_bits (wm8962->regmap,WM8962_EQ1 ,WM8962_EQ_SHARED_COEFF ,0 ); -/* Don't debouce interrupts so we don't need SYSCLK */ +/* Don't debounce interrupts so we don't need SYSCLK */ regmap_update_bits(wm8962->regmap, WM8962_IRQ_DEBOUNCE, WM8962_FLL_LOCK_DB | WM8962_PLL3_LOCK_DB | WM8962_PLL2_LOCK_DB | WM8962_TEMP_SHUT_DB,
sound/soc/codecs/wm8996.c +1 -1
@@ -2106,7 +2106,7 @@ static int wm8996_set_fll(struct snd_soc_component *component, int fll_id, int sif (i2c->irq) timeout *=10 ;else -/* ensure timeout of atleast 1 jiffies */ +/* ensure timeout of at least 1 jiffies */ timeout = (timeout/2 ) ? :1 ;for (retry =0 ; retry <10 ; retry++) {
sound/soc/codecs/wm_hubs.c +1 -1
@@ -338,7 +338,7 @@ static int wm8993_put_dc_servo(struct snd_kcontrol *kcontrol, ret =snd_soc_put_volsw (kcontrol, ucontrol);/* If we're applying an offset correction then updating the -* callibration would be likely to introduce further offsets. */ +* calibration would be likely to introduce further offsets. */ if (hubs->dcs_codes_l || hubs->dcs_codes_r || hubs->no_series_update)return ret;
Signature · 1 line
2.48.1
PATCH 2/3 firmware: cirrus: fix typo "upto" in comment
In reply to Hemanth SelamCorrect "upto" to "up to", reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes.
--- drivers/firmware/cirrus/cs_dsp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/firmware/cirrus/cs_dsp.c +1 -1
@@ -3505,7 +3505,7 @@ EXPORT_SYMBOL_NS_GPL(cs_dsp_chunk_write, "FW_CS_DSP");* * As cs_dsp_chunk_write only writes data when a whole DSP word is ready to * be written out it is possible that some data will remain in the cache, this -* function will pad that data with zeros upto a whole DSP word and write out. +* function will pad that data with zeros up to a whole DSP word and write out. * * Return: Zero for success, a negative number on error. */
Signature · 1 line
2.48.1
PATCH 3/3 mfd: fix typo "convertor" in comment
In reply to Hemanth SelamCorrect "convertor" to "converter", reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes.
--- drivers/mfd/wm831x-auxadc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mfd/wm831x-auxadc.c +1 -1
@@ -132,7 +132,7 @@ static irqreturn_t wm831x_auxadc_irq(int irq, void *irq_data) 1 << input, 0); wm831x->auxadc_active &= ~(1 << input); -/* Turn off the entire convertor if idle */ +/* Turn off the entire converter if idle */ if (!wm831x->auxadc_active)wm831x_reg_write (wm831x,WM831X_AUXADC_CONTROL ,0 );
Signature · 1 line
2.48.1
[email protected]
AI reviewRe: [PATCH 3/3] mfd: fix typo "convertor" in comment
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] The commit message prefix and capitalization violate the MFD subsystem guidelines. --
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The commit message prefix and capitalization violate the MFD subsystem guidelines. --
commit 9822de653028134dd1239ce2fd2798565ae60014
Author: Hemanth Selam <[email protected]>
mfd: fix typo "convertor" in comment
This commit corrects a typo ("convertor" to "converter") in a code comment within the wm831x-auxadc driver, as reported by checkpatch.
Quoted 1 line
mfd: fix typo "convertor" in comment
[Severity: Low]
Does this commit message subject follow the MFD subsystem naming conventions?
According to the MFD guidelines, the prefix format should include the driver name and capitalize the description, such as:
mfd: <Driver>: <Capitalized description>
For this patch, it might be better formatted as:
mfd: wm831x-auxadc: Fix typo "convertor" in comment
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=3