linux-kernel - Re: linux-next: build warning after merge of the drm-misc tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <cn3l445yzdhehsyyxurjn4x5stnyo34beogguupk7wsjqrloh5@d2berut7dn3l>
Date: Fri, 1 Aug 2025 13:30:52 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Andy Yan <andyshrk@....com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
        Simona Vetter <simona.vetter@...ll.ch>,
        Andy Yan <andy.yan@...k-chips.com>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-misc tree

On Fri, Aug 01, 2025 at 02:28:09PM +0800, Andy Yan wrote:
> 
> Hello，
> 
> At 2025-08-01 12:43:54, "Stephen Rothwell" <sfr@...b.auug.org.au> wrote:
> >Hi all,
> >
> >On Wed, 16 Jul 2025 20:31:15 +1000 Stephen Rothwell <sfr@...b.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.

I tried picking it up into the drm-misc-next-fixes branch, but I could
not do it: the offending commit is present in drm-misc-next-2025-07-17,
while drm-misc-next-fixes is based on drm-misc-next-2025-07-10.

-- 
With best wishes
Dmitry