From: Jocelyn Falempe <jfalempe@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll•ch>
Cc: 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: Tue, 16 Apr 2024 10:25:35 +0200 [thread overview]
Message-ID: <70ec563b-b6a8-48d6-9f9b-287b13df8f36@redhat.com> (raw)
In-Reply-To: <20240416173112.04579e40@canb.auug.org.au>
On 16/04/2024 09:31, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> drivers/gpu/drm/drm_fb_dma_helper.c:166: warning: Excess function parameter 'drm_scanout_buffer' description in 'drm_fb_dma_get_scanout_buffer'
> drivers/gpu/drm/drm_fb_dma_helper.c:166: warning: Function parameter or struct member 'sb' not described in 'drm_fb_dma_get_scanout_buffer'
> drivers/gpu/drm/drm_fb_dma_helper.c:166: warning: Excess function parameter 'drm_scanout_buffer' description in 'drm_fb_dma_get_scanout_buffer'
>
Hi,
Thanks for pointing that out. The parameter name is 'sb' and not
'drm_scanout_buffer', I will send a fix.
Best regards,
--
Jocelyn
> Introduced by commit
>
> 879b3b6511fe ("drm/fb_dma: Add generic get_scanout_buffer() for drm_panic")
>
next prev parent reply other threads:[~2024-04-16 8:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 7:31 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2024-04-16 8:25 ` Jocelyn Falempe [this message]
-- 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-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-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=70ec563b-b6a8-48d6-9f9b-287b13df8f36@redhat.com \
--to=jfalempe@redhat$(echo .)com \
--cc=daniel.vetter@ffwll$(echo .)ch \
--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 \
/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