From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simona Vetter <simona.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
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: Tue, 14 Jan 2025 16:41:49 +1100 [thread overview]
Message-ID: <20250114164149.6459996d@canb.auug.org.au> (raw)
In-Reply-To: <20241220154208.720d990b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hi all,
On Fri, 20 Dec 2024 15:42:08 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> drivers/gpu/drm/xlnx/zynqmp_dpsub.h:86: warning: Function parameter or struct member 'audio' not described in 'zynqmp_dpsub'
> drivers/gpu/drm/xlnx/zynqmp_dpsub.c:1: warning: no structured comments found
>
> Introduced by commit
>
> 3ec5c1579305 ("drm: xlnx: zynqmp_dpsub: Add DP audio support")
I am still seeing these warnings. That commit is now in the drm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-01-14 5:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 4:42 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2025-01-14 5:41 ` Stephen Rothwell [this message]
2025-01-16 10:34 ` Tomi Valkeinen
2025-01-16 11:50 ` Maxime Ripard
-- 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-06-11 4:09 Stephen Rothwell
2025-08-01 4:34 ` Stephen Rothwell
2025-08-01 11:04 ` Dmitry Baryshkov
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-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
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=20250114164149.6459996d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@redhat.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=simona.vetter@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
/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