From: Graham Whaley <graham.whaley@linux.intel.com>
To: daniel.vetter@intel.com, jani.nikula@linux.intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Graham Whaley <graham.whaley@linux.intel.com>,
danilo.cesar@collabora.co.uk, corbet@lwn.net
Subject: [PATCH 1/5] Documentation: drm: Fix pdfdocs sect/title tags
Date: Tue, 25 Aug 2015 10:26:41 +0100 [thread overview]
Message-ID: <1440494805-13325-2-git-send-email-graham.whaley@linux.intel.com> (raw)
In-Reply-To: <1440494805-13325-1-git-send-email-graham.whaley@linux.intel.com>
Building pdfdocs shows errors with !includes and <sect>s such as:
jade:/Documentation/DocBook/drm.xml:666:11:E: document type does not
allow element "para" here; missing one of "glossary", "bibliography",
"index" start-tag
Fix by adding <title> items and add/shuffle <sect>, <title> and !include
items.
Signed-off-by: Graham Whaley <graham.whaley@linux.intel.com>
---
Documentation/DocBook/drm.tmpl | 32 ++++++++++++++++++++++----------
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 66bc646..586f1b8 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -303,6 +303,9 @@ char *date;</synopsis>
</para>
!Edrivers/gpu/drm/drm_pci.c
!Edrivers/gpu/drm/drm_platform.c
+ </sect2>
+ <sect2>
+ <title>Calling Registration Directly</title>
<para>
New drivers that no longer rely on the services provided by the
<structname>drm_bus</structname> structure can call the low-level
@@ -2352,7 +2355,7 @@ void intel_crt_init(struct drm_device *dev)
</itemizedlist>
</sect2>
<sect2>
- <title>Atomic Modeset Helper Functions Reference</title>
+ <title>Atomic Modeset Helper Functions Introduction</title>
<sect3>
<title>Overview</title>
!Pdrivers/gpu/drm/drm_atomic_helper.c overview
@@ -2365,14 +2368,20 @@ void intel_crt_init(struct drm_device *dev)
<title>Atomic State Reset and Initialization</title>
!Pdrivers/gpu/drm/drm_atomic_helper.c atomic state reset and initialization
</sect3>
+ </sect2>
+ <sect2>
+ <title>Atomic Modeset Helper Functions Reference</title>
!Iinclude/drm/drm_atomic_helper.h
!Edrivers/gpu/drm/drm_atomic_helper.c
</sect2>
<sect2>
+ <title>Modeset Helper Functions Introduction</title>
+!Pdrivers/gpu/drm/drm_crtc_helper.c overview
+ </sect2>
+ <sect2>
<title>Modeset Helper Functions Reference</title>
!Iinclude/drm/drm_crtc_helper.h
!Edrivers/gpu/drm/drm_crtc_helper.c
-!Pdrivers/gpu/drm/drm_crtc_helper.c overview
</sect2>
<sect2>
<title>Output Probing Helper Functions Reference</title>
@@ -2432,8 +2441,8 @@ void intel_crt_init(struct drm_device *dev)
</sect2>
<sect2>
<title id="drm-kms-planehelpers">Plane Helper Reference</title>
-!Edrivers/gpu/drm/drm_plane_helper.c
!Pdrivers/gpu/drm/drm_plane_helper.c overview
+!Edrivers/gpu/drm/drm_plane_helper.c
</sect2>
<sect2>
<title>Tile group</title>
@@ -2449,6 +2458,9 @@ void intel_crt_init(struct drm_device *dev)
<title>Default bridge callback sequence</title>
!Pdrivers/gpu/drm/drm_bridge.c bridge callbacks
</sect3>
+ </sect2>
+ <sect2>
+ <title>Bridges Function Reference</title>
!Edrivers/gpu/drm/drm_bridge.c
</sect2>
</sect1>
@@ -4114,19 +4126,19 @@ int num_ioctls;</synopsis>
<sect2>
<title>GTT Fences and Swizzling</title>
!Idrivers/gpu/drm/i915/i915_gem_fence.c
- <sect3>
- <title>Global GTT Fence Handling</title>
+ </sect2>
+ <sect2>
+ <title>Global GTT Fence Handling</title>
!Pdrivers/gpu/drm/i915/i915_gem_fence.c fence register handling
- </sect3>
- <sect3>
- <title>Hardware Tiling and Swizzling Details</title>
+ </sect2>
+ <sect2>
+ <title>Hardware Tiling and Swizzling Details</title>
!Pdrivers/gpu/drm/i915/i915_gem_fence.c tiling swizzling details
- </sect3>
</sect2>
<sect2>
<title>Object Tiling IOCTLs</title>
-!Idrivers/gpu/drm/i915/i915_gem_tiling.c
!Pdrivers/gpu/drm/i915/i915_gem_tiling.c buffer object tiling
+!Idrivers/gpu/drm/i915/i915_gem_tiling.c
</sect2>
<sect2>
<title>Buffer Object Eviction</title>
--
2.4.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-25 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:26 [PATCH 0/5] Documentation: drm: Make drm.tmpl build as pdfdoc Graham Whaley
2015-08-25 9:26 ` Graham Whaley [this message]
2015-08-25 11:34 ` [PATCH 1/5] Documentation: drm: Fix pdfdocs sect/title tags Daniel Vetter
2015-08-25 14:42 ` Graham Whaley
2015-08-25 9:26 ` [PATCH 2/5] Documentation: drm: Fix pdfdocs listitem and abstract <para>s Graham Whaley
2015-08-25 9:26 ` [PATCH 3/5] Documentation: drm: Change <code> to <literal> Graham Whaley
2015-08-25 9:26 ` [PATCH 4/5] Documentation: drm: Convert KMS Properties HTML table to CALS Graham Whaley
2015-08-25 14:29 ` Daniel Vetter
2015-08-25 16:10 ` Graham Whaley
2015-08-26 9:32 ` [Intel-gfx] " Daniel Vetter
2015-09-01 17:56 ` Danilo Cesar Lemes de Paula
2015-09-02 9:22 ` Graham Whaley
2015-09-02 13:50 ` Graham Whaley
2015-08-25 9:26 ` [PATCH 5/5] Documentation: drm: Unify quoting methods Graham Whaley
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=1440494805-13325-2-git-send-email-graham.whaley@linux.intel.com \
--to=graham.whaley@linux.intel.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@intel.com \
--cc=danilo.cesar@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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