From: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
To: "Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>,
"Zack Rusin" <zack.rusin@broadcom.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Cc: Markus Schneider-Pargmann <msp@baylibre.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vmwgfx: Don't use UTS_RELEASE directly
Date: Wed, 10 Jun 2026 15:04:07 -0700 [thread overview]
Message-ID: <de7acf2e-e07c-4a94-92c7-ae0c9311c8a5@broadcom.com> (raw)
In-Reply-To: <20260504073422.1130008-2-u.kleine-koenig@baylibre.com>
On 5/4/26 12:34 AM, Uwe Kleine-König (The Capable Hub) 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 vmwgfx_drv.o.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
> Hello,
>
> an alternative way to address this is to drop the kernel version string
> completely. But I'm not sure how redundant this really is so I chose the
> init_utsname() approach.
>
> Best regards
> Uwe
>
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> index 0f101aedb49a..12f5f288ae15 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> @@ -24,7 +24,6 @@
> #include <drm/drm_sysfs.h>
> #include <drm/ttm/ttm_range_manager.h>
> #include <drm/ttm/ttm_placement.h>
> -#include <generated/utsrelease.h>
>
> #ifdef CONFIG_X86
> #include <asm/hypervisor.h>
> @@ -35,6 +34,7 @@
> #include <linux/dma-mapping.h>
> #include <linux/module.h>
> #include <linux/pci.h>
> +#include <linux/utsname.h>
> #include <linux/version.h>
> #include <linux/vmalloc.h>
>
> @@ -1115,7 +1115,7 @@ static int vmw_driver_load(struct vmw_private *dev_priv, u32 pci_id)
> vmw_print_sm_type(dev_priv);
> vmw_host_printf("vmwgfx: Module Version: %d.%d.%d (kernel: %s)",
> VMWGFX_DRIVER_MAJOR, VMWGFX_DRIVER_MINOR,
> - VMWGFX_DRIVER_PATCHLEVEL, UTS_RELEASE);
> + VMWGFX_DRIVER_PATCHLEVEL, init_utsname()->release);
> vmw_write_driver_id(dev_priv);
>
> dev_priv->pm_nb.notifier_call = vmwgfx_pm_notifier;
>
> base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
LGTM!
Reviewed-by: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
Sorry for missing this patch earlier. Unfortunately our maintainer Zack
is out for two weeks so we'll merge this patch at that time.
--
Maaz Mombasawala <maaz.mombasawala@broadcom.com>
next prev parent reply other threads:[~2026-06-10 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 7:34 Uwe Kleine-König (The Capable Hub)
2026-06-10 17:00 ` Uwe Kleine-König (The Capable Hub)
2026-06-10 22:04 ` Maaz Mombasawala [this message]
2026-07-19 17:49 ` Uwe Kleine-König (The Capable Hub)
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=de7acf2e-e07c-4a94-92c7-ae0c9311c8a5@broadcom.com \
--to=maaz.mombasawala@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=msp@baylibre.com \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
--cc=zack.rusin@broadcom.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
Powered by JetHome