summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2026-09-24 23:47:51 +0100
committerMark Brown <broonie@kernel.org>2026-09-24 23:47:51 +0100
commit27f7c1ad8da626f1785db2ec234558d07120403b (patch)
tree4654ac3921f868ec2011a7eb54a878f74b546b92 /scripts/Makefile.thinlto
parentb4136c0d69ead737197af741e20edd1c3574f6b4 (diff)
parent9f2933d9a437302d5ae32eb9022efef049d8ab22 (diff)
downloadlinux-27f7c1ad8da626f1785db2ec234558d07120403b.tar.gz
linux-27f7c1ad8da626f1785db2ec234558d07120403b.zip
ASoC: codecs: propagate component resume cache sync failures
Pengpeng Hou <pengpeng@iscas.ac.cn> says: Commit 951af101c730 ("ASoC: report component resume callback errors") made negative component resume results visible through the existing ASoC component error helper while preserving best-effort resume. These 14 component resume callbacks still discard the final regcache_sync() result and return success. Return that result so the common wrapper can report a failed cache replay with component context. None of these callbacks has dependent work after the sync, so the patches do not add rollback or retry semantics and do not change the successful path. The issues were found by a tool we developed. GPT-5 assisted with source-history review, patch construction and changelog drafting. No dynamic reproducer was produced. The series was not built or tested on codec hardware. The 14 patches were manually reviewed, checked with checkpatch.pl and applied in order to sound/for-next at 27a50351cbc8. The shared error-reporting contract was discussed at: https://lore.kernel.org/r/20260825085239.82282-1-pengpeng@iscas.ac.cn Link: https://patch.msgid.link/20260902013256.93072-1-pengpeng@iscas.ac.cn
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions