Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arnd Bergmann" <arnd@kernel.org>
Cc: Frank.Li@kernel.org, imx@lists.linux.dev,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/bridge: add missing drm/drm_panel.h inclusions
Date: Mon, 28 Sep 2026 16:31:16 +0000	[thread overview]
Message-ID: <20260928163116.903871F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260928161605.2271412-1-arnd@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/bridge: commit message and tree context mismatch
--

commit ac5ab6aba140c1bdb755618fe3998cc33d9cf30b
Author: Arnd Bergmann <arnd@arndb.de>

drm/bridge: add missing drm/drm_panel.h inclusions

This commit adds <drm/drm_panel.h> includes to various drm/bridge drivers.
The commit message states this is to fix implicit declaration build failures
after devm_drm_of_get_bridge() was moved to drm_panel.h.

>     The devm_drm_of_get_bridge() declaration moved to drm_panel.h, but
>     not all callers include this, which leads to build failures in
>     some configurations:
>     
>     drivers/gpu/drm/imx/lcdc/imx-lcdc.c: In function 'imx_lcdc_probe':
>     drivers/gpu/drm/imx/lcdc/imx-lcdc.c:404:18: error: implicit declaration of function 'devm_drm_of_get_bridge' [-Wimplicit-function-declaration]
>       404 |         bridge = devm_drm_of_get_bridge(dev, dev->of_node, 0, 0);
>           |                  ^~~~~~~~~~~~~~~~~~~~~~
>     drivers/gpu/drm/verisilicon/vs_bridge.c: In function 'vs_bridge_init':
>     drivers/gpu/drm/verisilicon/vs_bridge.c:306:16: error: implicit declaration of function 'devm_drm_of_get_bridge' [-Wimplicit-function-declaration]
>       306 |         next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,
>           |                ^~~~~~~~~~~~~~~~~~~~~~
>     
>     Include the new header in all files that need it.
>     
>     Fixes: aa8a8c7e4641 ("drm/bridge: panel: move all code to drm_panel.c")

[Severity: Medium]
Is the premise of this commit accurate for the current tree?

Looking at include/drm/drm_bridge.h, devm_drm_of_get_bridge() is still
declared there:

include/drm/drm_bridge.h:
	struct drm_bridge *devm_drm_of_get_bridge(struct device *dev, struct device_node *node,
						  u32 port, u32 endpoint);

Because the prerequisite commit aa8a8c7e4641 appears to be missing in this
tree, the declaration remains in drm_bridge.h and the mentioned build
failure does not exist here.

Does this patch depend on another series, or is it premature for this
particular branch?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260928161605.2271412-1-arnd@kernel.org?part=1

  reply	other threads:[~2026-09-28 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 16:04 [PATCH] drm/bridge: add missing drm/drm_panel.h inclusions Arnd Bergmann
2026-09-28 16:31 ` sashiko-bot [this message]
2026-09-28 22:20 ` Doug Anderson
2026-09-29  7:27 ` Luca Ceresoli
2026-09-29 10:39   ` Luca Ceresoli
2026-09-29 11:26   ` Arnd Bergmann

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=20260928163116.903871F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=arnd@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imx@lists.linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    /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