From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"u.kleine-koenig@baylibre.com" <u.kleine-koenig@baylibre.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drm/xe: Don't use UTS_RELEASE directly
Date: Tue, 28 Apr 2026 16:21:28 -0400 [thread overview]
Message-ID: <afEWyE8UIIWpixFU@intel.com> (raw)
In-Reply-To: <c039c23483b6b280806b8c7fa100f6de26e18ce0.camel@intel.com>
On Tue, Apr 28, 2026 at 04:01:41PM -0400, Souza, Jose wrote:
> On Tue, 2026-04-28 at 15:58 -0400, Rodrigo Vivi wrote:
> > On Tue, Apr 28, 2026 at 02:09:31PM +0300, Jani Nikula wrote:
> > > 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>
> >
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> >
> > Jose, ack on this?!
> >
> > I'm afraid this could break the current Mesa parser, so better
> > checking first...
> >
>
> It will not cause any problems.
>
> Acked-by: José Roberto de Souza <jose.souza@intel.com>
Thank you all, pushed to drm-xe-next
>
> > >
> > > > ---
> > > > 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
prev parent reply other threads:[~2026-04-28 20:21 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
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 [this message]
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=afEWyE8UIIWpixFU@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@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