summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorMaxime Ripard <mripard@kernel.org>2025-09-30 12:59:49 +0200
committerMaxime Ripard <mripard@kernel.org>2025-10-06 13:59:21 +0200
commitd8ebc4162fcd2fde6ae70168e6cb63bb64e93544 (patch)
tree8b39672479a2f1c7c1ae91d1acd3e19cb64cd0f3 /tools/perf/scripts/python/syscall-counts.py
parent653ce3a3f683673cb3f8904e08bffc144dd0e972 (diff)
downloadlinux-d8ebc4162fcd2fde6ae70168e6cb63bb64e93544.tar.gz
linux-d8ebc4162fcd2fde6ae70168e6cb63bb64e93544.zip
drm/framebuffer: Switch to drm_atomic_get_new_crtc_state()
The atomic_remove_fb() function uses the deprecated drm_atomic_get_existing_crtc_state() helper. Despite its name, this function builds and commit a new drm_atomic_state, and the call to drm_atomic_get_existing_crtc_state() is part of the state building, thus happening before the states are swapped. As such, the existing state points to the new state, and we can use drm_atomic_get_new_crtc_state() instead. Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://lore.kernel.org/r/20250930-drm-no-more-existing-state-v5-34-eeb9e1287907@kernel.org Signed-off-by: Maxime Ripard <mripard@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions