From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Matthew Auld <matthew.auld@intel.com>,
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: Thu, 3 Jun 2021 19:32:42 +1000 [thread overview]
Message-ID: <20210603193242.1ce99344@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/gpu/driver-uapi.rst:2412: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:1393.
Declaration is '.. c:enum:: drm_i915_gem_memory_class'.
Documentation/gpu/driver-uapi.rst:2484: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:2484.
Declaration is '.. c:struct:: drm_i915_gem_memory_class_instance'.
Documentation/gpu/driver-uapi.rst:7: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:7.
Declaration is '.. c:struct:: drm_i915_memory_region_info'.
Documentation/gpu/driver-uapi.rst:2531: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:2531.
Declaration is '.. c:struct:: drm_i915_query_memory_regions'.
Documentation/gpu/driver-uapi.rst:2595: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:1393.
Declaration is '.. c:struct:: drm_i915_gem_create_ext'.
Documentation/gpu/driver-uapi.rst:2615: WARNING: Duplicate C declaration, also defined at gpu/rfc/i915_gem_lmem:1393.
Declaration is '.. c:struct:: drm_i915_gem_create_ext_memory_regions'.
Introduced by (one or more of) commits
0c1a77cbdafb ("drm/doc: add section for driver uAPI")
2bc9c04ea702 ("drm/doc/rfc: i915 DG1 uAPI")
727ecd99a4c9 ("drm/doc/rfc: drop the i915_gem_lmem.h header")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-03 9:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 9:32 Stephen Rothwell [this message]
2021-07-08 2:20 ` linux-next: build warnings after merge of the drm tree 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
-- 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-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=20210603193242.1ce99344@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew.auld@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).