From: "Andy Yan" <andyshrk@163.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Simona Vetter" <simona.vetter@ffwll.ch>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Intel Graphics" <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re:linux-next: build failure after merge of the drm-misc tree
Date: Tue, 15 Jul 2025 13:51:32 +0800 (CST) [thread overview]
Message-ID: <4d2f67f5.4ec9.1980ca36770.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <20250715135511.63774cdb@canb.auug.org.au>
Hi all,
At 2025-07-15 11:55:11, "Stephen Rothwell" <sfr@canb.auug.org.au> wrote:
>Hi all,
>
>After merging the drm-misc tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>
>drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c: In function 'ge_b850v3_lvds_detect':
>drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:145:16: error: too few arguments to function 'ge_b850v3_lvds_bridge_detect'
> 145 | return ge_b850v3_lvds_bridge_detect(&ge_b850v3_lvds_ptr->bridge);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:124:1: note: declared here
> 124 | ge_b850v3_lvds_bridge_detect(struct drm_bridge *bridge, struct drm_connector *connector)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>drivers/gpu/drm/bridge/megachips-stdpxxxx-ge-b850v3-fw.c:146:1: error: control reaches end of non-void function [-Werror=return-type]
> 146 | }
> | ^
>
>Caused by commit
>
> 5d156a9c3d5e ("drm/bridge: Pass down connector to drm bridge detect hook")
Sorry for this, I have sent a fix for this issue:
https://lore.kernel.org/dri-devel/20250715054754.800765-1-andyshrk@163.com/T/#u
>
>I have used the drm-misc tree from next-20250714 for today.
>
>--
>Cheers,
>Stephen Rothwell
next prev parent reply other threads:[~2025-07-15 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 3:55 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2025-07-15 5:51 ` Andy Yan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 1:28 Stephen Rothwell
2024-02-06 12:39 ` Thomas Hellström
2024-02-06 20:21 ` Lucas De Marchi
2024-02-07 6:56 ` Thomas Hellström
2024-02-07 9:33 ` Jani Nikula
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=4d2f67f5.4ec9.1980ca36770.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona.vetter@ffwll.ch \
/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