summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2020-01-24 23:02:28 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2020-02-15 00:38:46 +0300
commit6e8a942b9ddc9b6b122e58a604bc3b452d2b8e8a (patch)
treebad83699acd29a5903fb087f5654758da41e7b82 /tools/perf/scripts/python/export-to-postgresql.py
parent4d23f48486240f6a5a43d1ff81bd44eee128b6a8 (diff)
downloadlinux-6e8a942b9ddc9b6b122e58a604bc3b452d2b8e8a.tar.xz
drm/edid: Document why we don't bounds check the DispID CEA block start/end
After much head scratching I managed to convince myself that for_each_displayid_db() has already done the bounds checks for the DispID CEA data block. Which is why we don't need to repeat them in cea_db_offsets(). To avoid having to go through that pain again in the future add a comment which explains this fact. Cc: Andres Rodriguez <andresx7@gmail.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200124200231.10517-5-ville.syrjala@linux.intel.com Acked-by: Alex Deucher <alexander.deucher@amd.com> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions