summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2026-07-30 22:30:58 +0100
committerMark Brown <broonie@kernel.org>2026-07-30 22:30:58 +0100
commitcd88e3d3e1ad570d69a89508b08906346c696aa7 (patch)
treee7a7bf51c2e38b69365bb029492c94b0946bc04f /tools/perf/scripts/python
parentc1d0a877c7be78eafa8b58ac3f4bf26f7d025765 (diff)
parent4075b9d256ef5c22688e2ae812c1b89ac791182a (diff)
ASoC: Intel: catpt: Code cleanup and renames
Cezary Rojewski <cezary.rojewski@intel.com> says: Direct follow up to the cleanup from June [1] and fixes from May [2]. Patches 4/8 and 5/8 is what I actually started with, several years ago when doing first attempts in addressing the long-standing problem [3]. With these, it is easy for a developer to move between the driver and the firmware repository. A clear example of why naming is imporant. Patches 2-8 carry no functional impact. Patch 1/8 slightly alters the suspend procedure as explained in its commit message. From practical perspective though, 1/8 too has no real impact on the functional flow. Changes found here reduce the code complexity slightly and rename a bunch of functions and variables. [1]: https://lore.kernel.org/all/20260603085827.1964796-1-cezary.rojewski@intel.com/ [2]: https://lore.kernel.org/linux-sound/20260528083444.1439233-1-cezary.rojewski@intel.com/ [3]: https://lore.kernel.org/linux-sound/20260528083444.1439233-2-cezary.rojewski@intel.com/ Link: https://patch.msgid.link/20260729110057.342447-1-cezary.rojewski@intel.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions