All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm/fbdev: Move fbdev helpers into client library
Date: Fri, 25 Sep 2026 07:34:10 +0000	[thread overview]
Message-ID: <20260925073410.BD4371F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260925071933.44283-3-tzimmermann@suse.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] kbuild: link error when GEM helpers are built-in and DRM_CLIENT_LIB is modular
--

commit d69668549441f21758d69fc518df18536eb9bb24
Author: Thomas Zimmermann <tzimmermann@suse.de>
Subject: drm/fbdev: Move fbdev helpers into client library

This commit moves DRM's fbdev emulation helpers into the client library
module and renames them from drm_fb_helper to drm_fbdev_helper.

> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
[ ... ]
> @@ -256,7 +255,6 @@ config DRM_TTM_HELPER
>  	tristate
>  	depends on DRM
>  	select DRM_TTM
> -	select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
>  	select FB_CORE if DRM_FBDEV_EMULATION
>  	select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
>  	help

[Severity: Low]
When DRM_KMS_HELPER is removed here, is there a replacement needed for the
client library? If a built-in driver selects DRM_TTM_HELPER=y and
DRM_FBDEV_EMULATION=y, but a modular driver forces DRM_CLIENT_LIB=m, can
this result in a vmlinux link error because the fbdev emulation code in
the client library is not built-in?

> @@ -265,7 +263,6 @@ config DRM_TTM_HELPER
>  config DRM_GEM_DMA_HELPER
>  	tristate
>  	depends on DRM
> -	select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
>  	select FB_CORE if DRM_FBDEV_EMULATION
>  	select FB_DMAMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
>  	help

[Severity: Low]
Does this missing replacement for the client library dependency also leave
config DRM_GEM_DMA_HELPER susceptible to the same link error when built-in?

> @@ -274,7 +271,6 @@ config DRM_GEM_DMA_HELPER
>  config DRM_GEM_SHMEM_HELPER
>  	tristate
>  	depends on DRM && MMU
> -	select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
>  	select FB_CORE if DRM_FBDEV_EMULATION
>  	select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
>  	help

[Severity: Low]
Similarly, should config DRM_GEM_SHMEM_HELPER select the client library to
prevent a link error when DRM_FBDEV_EMULATION is enabled?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260925071933.44283-1-tzimmermann@suse.de?part=2

  reply	other threads:[~2026-09-25  7:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  7:17 [PATCH v3 0/2] drm/fbdev: Move helpers to clients/ subdirectory Thomas Zimmermann
2026-09-25  7:17 ` Thomas Zimmermann
2026-09-25  7:17 ` Thomas Zimmermann
2026-09-25  7:17 ` [PATCH v3 1/2] drm/fbdev: Move fbdev module parameters next to module init Thomas Zimmermann
2026-09-25  7:17   ` Thomas Zimmermann
2026-09-25  7:17   ` Thomas Zimmermann
2026-09-25  7:17 ` [PATCH v3 2/2] drm/fbdev: Move fbdev helpers into client library Thomas Zimmermann
2026-09-25  7:17   ` Thomas Zimmermann
2026-09-25  7:17   ` Thomas Zimmermann
2026-09-25  7:34   ` sashiko-bot [this message]
2026-09-25  7:26 ` ✗ CI.checkpatch: warning for drm/fbdev: Move helpers to clients/ subdirectory (rev3) Patchwork
2026-09-25  7:28 ` ✓ CI.KUnit: success " Patchwork
2026-09-25  8:05 ` ✓ i915.CI.BAT: " Patchwork
2026-09-25  8:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-25 16:39 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-26  2:18 ` ✓ i915.CI.Full: success " Patchwork

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=20260925073410.BD4371F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.