From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Simona Vetter <simona.vetter@ffwll•ch>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro•org>,
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 warnings after merge of the drm-misc tree
Date: Fri, 1 Aug 2025 14:34:40 +1000 [thread overview]
Message-ID: <20250801143440.59e13a4b@canb.auug.org.au> (raw)
In-Reply-To: <20250611140933.1429a1b8@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Hi all,
On Wed, 11 Jun 2025 14:09:33 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/drm/drm_bridge.h:943: warning: Function parameter or struct member 'hdmi_cec_init' not described in 'drm_bridge_funcs'
> include/drm/drm_bridge.h:943: warning: Function parameter or struct member 'hdmi_cec_enable' not described in 'drm_bridge_funcs'
> include/drm/drm_bridge.h:943: warning: Function parameter or struct member 'hdmi_cec_log_addr' not described in 'drm_bridge_funcs'
> include/drm/drm_bridge.h:943: warning: Function parameter or struct member 'hdmi_cec_transmit' not described in 'drm_bridge_funcs'
>
> Introduced by commit
>
> a74288c8ded7 ("drm/display: bridge-connector: handle CEC adapters")
I am still seeing these warnings. That commit is now in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-01 4:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 4:09 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2025-08-01 4:34 ` Stephen Rothwell [this message]
2025-08-01 11:04 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 0:56 Stephen Rothwell
2025-11-10 2:50 Stephen Rothwell
2025-11-10 2:24 Stephen Rothwell
2025-11-05 5:18 Stephen Rothwell
2025-06-18 5:13 Stephen Rothwell
2025-01-06 6:46 Stephen Rothwell
2025-01-14 5:43 ` Stephen Rothwell
2025-01-14 11:40 ` Dmitry Baryshkov
2025-01-14 12:06 ` Stephen Rothwell
2024-12-20 4:42 Stephen Rothwell
2025-01-14 5:41 ` Stephen Rothwell
2025-01-16 10:34 ` Tomi Valkeinen
2025-01-16 11:50 ` Maxime Ripard
2024-10-10 5:09 Stephen Rothwell
2024-10-10 8:35 ` Thomas Hellström
2024-10-10 5:04 Stephen Rothwell
2024-08-01 6:03 Stephen Rothwell
2024-04-16 7:31 Stephen Rothwell
2024-04-16 8:25 ` Jocelyn Falempe
2024-03-26 5:12 Stephen Rothwell
2023-12-04 4:53 Stephen Rothwell
2023-03-14 3:15 Stephen Rothwell
2022-06-11 8:21 Stephen Rothwell
2022-06-11 16:57 ` Doug Anderson
2022-04-06 5:44 Stephen Rothwell
2022-04-06 5:51 ` Stephen Rothwell
2022-04-13 0:07 ` Stephen Rothwell
2021-01-15 1:23 Stephen Rothwell
2021-01-15 15:03 ` Nirmoy
2015-08-14 5:35 Stephen Rothwell
2015-08-14 12:51 ` Thierry Reding
2015-07-14 3:05 Stephen Rothwell
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=20250801143440.59e13a4b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--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=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