From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, corbet@lwn.net, skhan@linuxfoundation.org
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation/gpu: resolve kerneldoc duplicate declaration warning
Date: Wed, 18 Mar 2026 20:06:12 +0530 [thread overview]
Message-ID: <20260318143612.2533863-1-sanjayembedded@gmail.com> (raw)
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
kernel-doc build with `make htmldocs` reports following WARNINGS.
Documentation/gpu/drm-kms:360: ../drivers/gpu/drm/drm_fourcc.c:397:
WARNING: Duplicate C declaration, also defined at gpu/drm-kms:35.
Declaration is '.. c:function::
const struct drm_format_info * drm_format_info (u32 format)'.
Documentation/gpu/drm-kms:491: ../drivers/gpu/drm/drm_modeset_lock.c:377:
WARNING: Duplicate C declaration, also defined at gpu/drm-kms:48.
Declaration is '.. c:function:: int drm_modeset_lock
(struct drm_modeset_lock *lock, struct drm_modeset_acquire_ctx *ctx)'.
Documentation/gpu/drm-uapi:607: ../drivers/gpu/drm/drm_ioctl.c:923:
WARNING: Duplicate C declaration, also defined at gpu/drm-uapi:69.
Declaration is '.. c:function::
bool drm_ioctl_flags (unsigned int nr, unsigned int *flags)'.
Add :no-identifiers: to prevent duplicate identifier generation and
keep the function documented at its implementation site.
No functional change.
Link: https://lore.kernel.org/oe-kbuild-all/202512302319.1PGGt3CN-lkp@intel.com/
Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
---
Documentation/gpu/drm-kms.rst | 2 ++
Documentation/gpu/drm-uapi.rst | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
index 2292e65f044c..0f0f90b3186d 100644
--- a/Documentation/gpu/drm-kms.rst
+++ b/Documentation/gpu/drm-kms.rst
@@ -356,6 +356,7 @@ Format Functions Reference
.. kernel-doc:: include/drm/drm_fourcc.h
:internal:
+ :no-identifiers: drm_format_info
.. kernel-doc:: drivers/gpu/drm/drm_fourcc.c
:export:
@@ -487,6 +488,7 @@ KMS Locking
.. kernel-doc:: include/drm/drm_modeset_lock.h
:internal:
+ :no-identifiers: drm_modeset_lock
.. kernel-doc:: drivers/gpu/drm/drm_modeset_lock.c
:export:
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index d98428a592f1..73b49e0dcda8 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -603,6 +603,7 @@ DRM specific patterns. Note that ENOTTY has the slightly unintuitive meaning of
.. kernel-doc:: include/drm/drm_ioctl.h
:internal:
+ :no-identifiers: drm_ioctl_flags
.. kernel-doc:: drivers/gpu/drm/drm_ioctl.c
:export:
@@ -761,4 +762,4 @@ Stable uAPI events
From ``drivers/gpu/drm/scheduler/gpu_scheduler_trace.h``
.. kernel-doc:: drivers/gpu/drm/scheduler/gpu_scheduler_trace.h
- :doc: uAPI trace events
\ No newline at end of file
+ :doc: uAPI trace events
--
2.34.1
reply other threads:[~2026-03-18 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260318143612.2533863-1-sanjayembedded@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
/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