From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@redhat.com>
Cc: "José Roberto de Souza" <jose.souza@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@intel.com>,
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: linux-next: build warnings after merge of the drm tree
Date: Mon, 19 Feb 2024 16:21:04 +1100 [thread overview]
Message-ID: <20240219162104.2843ada2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (htmldocs) produced
these warnings:
include/uapi/drm/i915_drm.h:3579: warning: Function parameter or struct member 'branch' not described in 'drm_i915_query_guc_submission_version'
include/uapi/drm/i915_drm.h:3579: warning: Function parameter or struct member 'major' not described in 'drm_i915_query_guc_submission_version'
include/uapi/drm/i915_drm.h:3579: warning: Function parameter or struct member 'minor' not described in 'drm_i915_query_guc_submission_version'
include/uapi/drm/i915_drm.h:3579: warning: Function parameter or struct member 'patch' not described in 'drm_i915_query_guc_submission_version'
Introduced by commit
b11236486749 ("drm/i915: Add GuC submission interface version query")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-19 5:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 5:21 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-13 6:29 linux-next: build warnings after merge of the drm tree 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
2021-04-01 7:32 Stephen Rothwell
2021-04-21 6:30 ` 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
2017-11-01 3:16 Stephen Rothwell
2017-11-01 9:58 ` Boris Brezillon
2017-05-19 2:07 Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25 1:49 ` Stephen Rothwell
2017-06-02 3:59 ` Stephen Rothwell
2017-06-02 21:05 ` Eric Anholt
2017-06-02 23:40 ` Stephen Rothwell
2017-06-03 0:45 ` Eric Anholt
2017-06-03 1:26 ` Stephen Rothwell
2017-02-23 23:27 Stephen Rothwell
2017-02-19 23:48 Stephen Rothwell
2012-10-04 2:21 Stephen Rothwell
2012-09-04 3:58 Stephen Rothwell
2012-09-04 5:31 ` Guenter Roeck
2012-09-04 6:40 ` Sedat Dilek
2012-09-04 8:22 ` Dave Airlie
2012-09-04 8:58 ` Sedat Dilek
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=20240219162104.2843ada2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tvrtko.ursulin@intel.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;
as well as URLs for NNTP newsgroup(s).