public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Uwe Kleine-König (The Capable Hub)"
	<u.kleine-koenig@baylibre.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/xe: Don't use UTS_RELEASE directly
Date: Tue, 28 Apr 2026 14:09:31 +0300	[thread overview]
Message-ID: <be82fd356047513f23a3193d8007a2e5e8d97e35@intel.com> (raw)
In-Reply-To: <20260428102527.189593-2-u.kleine-koenig@baylibre.com>

On Tue, 28 Apr 2026, Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com> wrote:
> 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>

> ---
> Hello,
>
> (implicit) v1 of this patch is available at 
> https://lore.kernel.org/20260427160902.1126027-2-u.kleine-koenig%40baylibre.com.
>
> The only changes since then is that instead of dropping the kernel line,
> init_utsname()->release is used, which is nearly what Jani Nikula
> suggested.

Almost the same, but better. ;)

I wonder if most UTS_RELEASE uses in the kernel should be changed the
same way?


BR,
Jani.


>
> Best regards
> Uwe
>
>  drivers/gpu/drm/xe/xe_devcoredump.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c
> index 558a1a9841a0..07c7c89240d8 100644
> --- a/drivers/gpu/drm/xe/xe_devcoredump.c
> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c
> @@ -8,7 +8,7 @@
>  
>  #include <linux/ascii85.h>
>  #include <linux/devcoredump.h>
> -#include <generated/utsrelease.h>
> +#include <linux/utsname.h>
>  
>  #include <drm/drm_managed.h>
>  
> @@ -101,7 +101,7 @@ static ssize_t __xe_devcoredump_read(char *buffer, ssize_t count,
>  
>  	drm_puts(&p, "**** Xe Device Coredump ****\n");
>  	drm_printf(&p, "Reason: %s\n", ss->reason);
> -	drm_puts(&p, "kernel: " UTS_RELEASE "\n");
> +	drm_printf(&p, "kernel: %s\n", init_utsname()->release);
>  	drm_puts(&p, "module: " KBUILD_MODNAME "\n");
>  
>  	ts = ktime_to_timespec64(ss->snapshot_time);
>
> base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-04-28 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 10:25 [PATCH v2] drm/xe: Don't use UTS_RELEASE directly Uwe Kleine-König (The Capable Hub)
2026-04-28 11:09 ` Jani Nikula [this message]
2026-04-28 13:32   ` Uwe Kleine-König (The Capable Hub)
2026-04-28 19:58   ` Rodrigo Vivi
2026-04-28 20:01     ` Souza, Jose
2026-04-28 20:21       ` Rodrigo Vivi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be82fd356047513f23a3193d8007a2e5e8d97e35@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=u.kleine-koenig@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox