summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorRichard Fitzgerald <rf@opensource.cirrus.com>2026-11-04 11:36:10 +0000
committerTakashi Iwai <tiwai@suse.de>2026-11-05 08:54:46 +0100
commitaebc5461e2d0ef8f09920dfbc90e05b427aa5d35 (patch)
tree669605374c64de1f670a5bceff56ee2aa3b10706 /scripts/Makefile.thinlto
parentd2895945d37e3426191894a010f94db31c206e10 (diff)
downloadlinux-next-aebc5461e2d0ef8f09920dfbc90e05b427aa5d35.tar.gz
linux-next-aebc5461e2d0ef8f09920dfbc90e05b427aa5d35.zip
ALSA: doc: cs35l56: Update calibration write failure message info
Update the descriptions of the "Failed to write calibration" and "Calibration disabled due to missing firmware controls" error messages. Originally "Failed to write calibration" was described as having the same cause as "Calibration disabled due to missing firmware controls". This was _typically_ true because the most likely cause of the write failure was missing controls (because both messages would be logged in that case). But it wasn't clear from the description that this was referring to the _typical_ root cause being the same. Reword the "Failed to write calibration" info to describe the possible other reasons for this error. Also slightly reword the description of "Calibration disabled due to missing firmware controls" to say "firmware wmfw file" instead of only "wmfw" and fix a missing "the" in the second bullet point. Also note that this is not necessarily an error, only information. Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com> Link: https://patch.msgid.link/20261104113610.1057194-1-rf@opensource.cirrus.com Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions