aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/reset/ssh:/git@git.zx2c4.com
diff options
context:
space:
mode:
authorUwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>2026-04-28 16:45:53 +0200
committerRob Clark <robin.clark@oss.qualcomm.com>2026-05-15 07:24:02 -0700
commit3f9ed5f5aa9ecffd284218fffd6abc29617f51d5 (patch)
tree031c4d12bb96cd76ab9dd67a5f3fae0016d36de1 /include/linux/reset/ssh:/git@git.zx2c4.com
parentdrm/msm/a6xx: Check kzalloc return in a8xx_hfi_send_perf_table (diff)
drm/msm: Don't use UTS_RELEASE directly
UTS_RELEASE evaluates to a static string and changes quite easily (e.g. uncommitted changes in the source tree or new commits). So when checking if a patch introduces changes to the resulting binary each usage of UTS_RELEASE is source of annoyance. Instead of using UTS_RELEASE directly use init_utsname()->release which evaluates to the same string but with that a change of UTS_RELEASE doesn't affect msm_disp_snapshot_util.o or msm_gpu.o. Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com> Patchwork: https://patchwork.freedesktop.org/patch/721948/ Message-ID: <20260428144553.1103785-2-u.kleine-koenig@baylibre.com> Signed-off-by: Rob Clark <robin.clark@oss.qualcomm.com>
Diffstat (limited to 'include/linux/reset/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions