From: sashiko-bot@kernel.org
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/fbdev: Move fbdev helpers into client library
Date: Wed, 23 Sep 2026 11:16:05 +0000 [thread overview]
Message-ID: <20260923111605.D7CB61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923110537.451614-3-tzimmermann@suse.de>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] drm: build failure in armada driver due to missing header rename
- [Low] drm: sphinx documentation build fails due to un-updated kernel-doc paths
--
commit eec385087eda413784c5684a793dc7987f6f4f49
Author: Thomas Zimmermann <tzimmermann@suse.de>
drm/fbdev: Move fbdev helpers into client library
This commit moves DRM's fbdev helpers into the client-library module and
fixes include statements throughout the DRM drivers. It also renames the
files from drm_fb_helper to drm_fbdev_helper.
> diff --git a/include/drm/drm_fb_helper.h b/include/drm/clients/drm_fbdev_helper.h
> similarity index 99%
> rename from include/drm/drm_fb_helper.h
> rename to include/drm/clients/drm_fbdev_helper.h
> index 0c5e5ed7b5e74..7575aaf34c620 100644
> --- a/include/drm/drm_fb_helper.h
> +++ b/include/drm/clients/drm_fbdev_helper.h
[Severity: Low]
Does drivers/gpu/drm/armada/armada_fbdev.c need to be updated to include the
new header path? This file still includes the old header path, which causes
a build failure because the header was renamed:
drivers/gpu/drm/armada/armada_fbdev.c:
#include <drm/drm_fb_helper.h>
[Severity: Low]
Do the kernel-doc directives in Documentation/gpu/drm-kms-helpers.rst need
to be updated? These directives reference the old file paths, breaking the
Sphinx documentation build:
Documentation/gpu/drm-kms-helpers.rst:
.. kernel-doc:: drivers/gpu/drm/drm_fb_helper.c
:doc: fbdev helpers
.. kernel-doc:: include/drm/drm_fb_helper.h
:internal:
.. kernel-doc:: drivers/gpu/drm/drm_fb_helper.c
:export:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923110537.451614-1-tzimmermann@suse.de?part=2
next prev parent reply other threads:[~2026-09-23 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:59 [PATCH 0/2] drm/fbdev: Move helpers to clients/ subdirectory Thomas Zimmermann
2026-09-23 10:59 ` [PATCH 1/2] drm/fbdev: Move fbdev module parameters next to module init Thomas Zimmermann
2026-09-23 10:59 ` [PATCH 2/2] drm/fbdev: Move fbdev helpers into client library Thomas Zimmermann
2026-09-23 11:16 ` sashiko-bot [this message]
2026-09-23 13:12 ` Jani Nikula
2026-09-23 12:17 ` ✓ i915.CI.BAT: success for drm/fbdev: Move helpers to clients/ subdirectory Patchwork
2026-09-23 13:03 ` [PATCH 0/2] " Deucher, Alexander
2026-09-24 5:25 ` ✗ i915.CI.Full: failure for " 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=20260923111605.D7CB61F000FF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox