From: Uma Shankar <uma.shankar@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: jonas@kwiboo.se, seanpaul@chromium.org
Subject: [v2 1/3] drm: ADD UAPI structure definition section in kernel doc
Date: Mon, 3 Jun 2019 18:38:48 +0530 [thread overview]
Message-ID: <1559567330-25182-2-git-send-email-uma.shankar@intel.com> (raw)
In-Reply-To: <1559567330-25182-1-git-send-email-uma.shankar@intel.com>
Add a new section for UAPI structure and helper definitions
in kernel docbook.
Suggested-by: Daniel Vetter <daniel@ffwll.ch>
Signed-off-by: Uma Shankar <uma.shankar@intel.com>
---
Documentation/gpu/drm-uapi.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index f368e58..94f9052 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -329,3 +329,12 @@ DRM_IOCTL_MODESET_CTL
mode setting, since on many devices the vertical blank counter is
reset to 0 at some point during modeset. Modern drivers should not
call this any more since with kernel mode setting it is a no-op.
+
+Userspace API Structures
+========================
+
+.. kernel-doc:: include/uapi/drm/drm_mode.h
+ :doc: overview
+
+.. kernel-doc:: include/uapi/drm/drm_mode.h
+ :internal:
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-03 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 13:08 [v2 0/3] Document fixes for DRM UAPI and HDR Uma Shankar
2019-06-03 13:08 ` Uma Shankar [this message]
2019-06-03 13:08 ` [v2 2/3] drm: Fix docbook warnings in hdr metadata helper structures Uma Shankar
2019-06-03 13:08 ` [v2 3/3] video/hdmi: Dropped static functions from kernel doc Uma Shankar
2019-06-03 13:46 ` ✗ Fi.CI.BAT: failure for Document fixes for DRM UAPI and HDR (rev2) Patchwork
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=1559567330-25182-2-git-send-email-uma.shankar@intel.com \
--to=uma.shankar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=seanpaul@chromium.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