DocBook/drm: Use an <itemizelist> for fundamental GEM operations

Signed-off-by: Michael Witten <mfwitten@gmail.com>
git-mirror · Aug 29, 2011 · 0c2d91a · 0c2d91a
1 parent f877bd4
commit 0c2d91a
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
@@ -709,9 +709,13 @@ void intel_crt_init(struct drm_device *dev)
 	read &amp; write, mapping, and domain ownership transfers.
       </para>
       <para>
-	On a fundamental level, GEM involves several operations: memory
-	allocation and freeing, command execution, and aperture management
-	at command execution time.  Buffer object allocation is relatively
+	On a fundamental level, GEM involves several operations:
+	<itemizedlist>
+	  <listitem>Memory allocation and freeing</listitem>
+	  <listitem>Command execution</listitem>
+	  <listitem>Aperture management at command execution time</listitem>
+	</itemizedlist>
+	Buffer object allocation is relatively
 	straightforward and largely provided by Linux's shmem layer, which
 	provides memory to back each object.  When mapped into the GTT
 	or used in a command buffer, the backing pages for an object are