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:Re: linux-next: build warning after merge of the drm-misc tree
Date: Fri, 1 Aug 2025 14:28:09 +0800 (CST) [thread overview]
Message-ID: <7304e450.4ca8.198645108de.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <20250801144354.0ac00f39@canb.auug.org.au>
Hello，
At 2025-08-01 12:43:54, "Stephen Rothwell" <sfr@canb•auug.org.au> wrote:
>Hi all,
>
>On Wed, 16 Jul 2025 20:31:15 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>> After merging the drm-misc tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> drivers/gpu/drm/drm_bridge.c:1242: warning: Function parameter or struct member 'connector' not described in 'drm_bridge_detect'
>>
>> Introduced by commit
>>
>> 5d156a9c3d5e ("drm/bridge: Pass down connector to drm bridge detect hook")
>
>I am still seeing that warning. That commit is now in Linus' tree.
The fix is here：
https://lore.kernel.org/dri-devel/20250716125602.3166573-1-andyshrk@163.com/
Hope that a Maintainer can review and apply it.
>
>--
>Cheers,
>Stephen Rothwell
next prev parent reply other threads:[~2025-08-01 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:31 linux-next: build warning after merge of the drm-misc tree Stephen Rothwell
2025-07-16 13:00 ` Andy Yan
2025-07-17 2:21 ` linux-next: " Randy Dunlap
2025-08-01 4:43 ` Stephen Rothwell
2025-08-01 6:28 ` Andy Yan [this message]
2025-08-01 10:30 ` Dmitry Baryshkov
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=7304e450.4ca8.198645108de.Coremail.andyshrk@163.com \
--to=andyshrk@163$(echo .)com \
--cc=andy.yan@rock-chips$(echo .)com \
--cc=dmitry.baryshkov@oss$(echo .)qualcomm.com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=simona.vetter@ffwll$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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