aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-memset.c
diff options
context:
space:
mode:
authorMatt Roper <[email protected]>2023-09-06 16:47:34 -0700
committerMatt Roper <[email protected]>2023-09-08 15:45:07 -0700
commit7ed888fa78129941255af09eddbf4cc51a3351d1 (patch)
tree00428de5cedd54ea19ef0eecce10e3c3a658b573 /lib/test_fortify/write_overflow-memset.c
parent231b1d6c9ab6ff23f7a1826835946dd2b0f57156 (diff)
drm/i915: Stop forcing clock gating init for future platforms
In the early days of i915, pretty much every platform needed to initialize _something_ in the clock gating init functions. In some cases the items initialized were inside the GT (and really should have been initialized through the GT workaround infrastructure instead). In other cases they were display programming (sometimes not even related to "clock gating" at all!) which probably needs to move inside the display-specific code. The number of initialization tasks that are truly "clock gating" and don't fall within the GT or display domains is relatively limited. Let's stop forcing future platforms to always define a clock gating init hook. Signed-off-by: Matt Roper <[email protected]> Reviewed-by: Lucas De Marchi <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-memset.c')
0 files changed, 0 insertions, 0 deletions