summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/export-to-postgresql-report
diff options
context:
space:
mode:
authorMaxime Ripard <mripard@kernel.org>2023-12-14 13:09:15 +0300
committerMaxime Ripard <mripard@kernel.org>2023-12-18 13:45:34 +0300
commitab9fabeae4e71095d29216ff14f8a56e4fdda895 (patch)
tree13c4c457e5e8e461e23c2eaebe0068ce26d6d6ea /tools/perf/scripts/python/bin/export-to-postgresql-report
parent17beda5e951aac35fee26703719c252bb216b56b (diff)
downloadlinux-ab9fabeae4e71095d29216ff14f8a56e4fdda895.tar.xz
drm/atomic: Make the drm_atomic_state documentation less ambiguous
The current documentation of drm_atomic_state says that it's the "global state object". This is confusing since, while it does contain all the objects affected by an update and their respective states, if an object isn't affected by this update it won't be part of it. Thus, it's not truly a "global state", unlike object state structures that do contain the entire state of a given object. Reviewed-by: Hamza Mahfooz <hamza.mahfooz@amd.com> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com> Link: https://lore.kernel.org/r/20231214100917.277842-4-mripard@kernel.org Signed-off-by: Maxime Ripard <mripard@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions