]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
drm/xe: Don't use UTS_RELEASE directly
authorUwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
Tue, 28 Apr 2026 10:25:25 +0000 (12:25 +0200)
committerRodrigo Vivi <rodrigo.vivi@intel.com>
Tue, 28 Apr 2026 20:20:33 +0000 (16:20 -0400)
commit3096d3e9f44afe011d2017ddade416924e1c99d5
tree02e12fb167a035606292fa74443e9efe9b0d73d5
parente70d1c5fedfac919278a96aae0984f1927a55137
drm/xe: 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 xe_devcoredump.o.

Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Acked-by: José Roberto de Souza <jose.souza@intel.com>
Link: https://patch.msgid.link/20260428102527.189593-2-u.kleine-koenig@baylibre.com
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
drivers/gpu/drm/xe/xe_devcoredump.c