From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Wed, 21 Apr 2021 16:30:31 +1000 [thread overview]
Message-ID: <20210421163031.10ef514b@canb.auug.org.au> (raw)
In-Reply-To: <20210401183234.11344d79@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 1093 bytes --]
Hi all,
On Thu, 1 Apr 2021 18:32:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'jump_whitelist' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'shadow_map' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'batch_map' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'
>
> Introduced by commit
>
> 0edbb9ba1bfe ("drm/i915: Move cmd parser pinning to execbuffer")
I am still seeing these warnings (as of next-20210420).
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-21 6:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 7:32 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2021-04-21 6:30 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-19 5:21 Stephen Rothwell
2023-06-13 6:29 Stephen Rothwell
2023-01-05 3:47 Stephen Rothwell
2021-06-03 9:32 Stephen Rothwell
2021-07-08 2:20 ` Stephen Rothwell
2021-08-10 9:26 ` Stephen Rothwell
2021-08-10 10:14 ` Daniel Vetter
2021-08-10 10:38 ` Stephen Rothwell
2021-08-10 10:50 ` Daniel Vetter
2021-08-10 11:01 ` Stephen Rothwell
2021-08-10 12:39 ` Daniel Vetter
2021-08-10 13:21 ` Stephen Rothwell
2020-11-05 6:50 Stephen Rothwell
2020-11-15 23:44 ` Stephen Rothwell
2020-12-14 19:50 ` Stephen Rothwell
2020-12-15 2:47 ` Stephen Rothwell
2020-12-15 9:42 ` Daniel Vetter
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=20210421163031.10ef514b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).