Fix build warnings on Latex

Fix the following issues:
- flattened-format.rst: improperly formed bullet list
- introduction.rst: section heading too short
- rename prolog.rst to rst_prolog so Sphinx doesn't try to process it
  directly

Signed-off-by: Grant Likely <[email protected]>

Author: glikely

source/conf.py

@@ -81,7 +81,7 @@
 exclude_patterns = []
 
 # Include at the beginning of every source file that is read
-with open('prolog.rst', 'rb') as pr:
+with open('rst_prolog', 'rb') as pr:
     rst_prolog = pr.read().decode('utf-8')
 
 # The reST default role (used for this markup: `text`) to use for all

source/flattened-format.rst

@@ -329,18 +329,23 @@ a whole.
 More precisely, each node’s representation consists of the following
 components:
 
-*  (optionally) any number of FDT_NOP tokens
-*  FDT_BEGIN_NODE token
- *  The node’s name as a null-terminated string
- *  [zeroed padding bytes to align to a 4-byte boundary]
-*  For each property of the node:
- *  (optionally) any number of FDT_NOP tokens
- *  FDT_PROP token
-  *  property information as given in section :ref:`sect-fdt-lexical-structure`
-  *  [zeroed padding bytes to align to a 4-byte boundary]
-*  Representations of all child nodes in this format
-*  (optionally) any number of FDT_NOP tokens
-*  FDT_END_NODE token
+* (optionally) any number of FDT_NOP tokens
+* FDT_BEGIN_NODE token
+
+   * The node’s name as a null-terminated string
+   * [zeroed padding bytes to align to a 4-byte boundary]
+
+* For each property of the node:
+
+   * (optionally) any number of FDT_NOP tokens
+   * FDT_PROP token
+
+      * property information as given in section :ref:`sect-fdt-lexical-structure`
+      * [zeroed padding bytes to align to a 4-byte boundary]
+
+* Representations of all child nodes in this format
+* (optionally) any number of FDT_NOP tokens
+* FDT_END_NODE token
 
 Note that this process requires that all property definitions for a
 particular node precede any subnode definitions for that node. Although

source/introduction.rst

@@ -79,7 +79,7 @@ Syntax* form. See section :ref:`chapter-devicetree-source-format` for
 an overview of this syntax.
 
 Relationship to IEEE™ 1275 and |epapr|
-------------------------------------
+--------------------------------------
 
 |spec| is loosely related to the IEEE 1275 Open Firmware
 standard—\ *IEEE Standard for Boot (Initialization Configuration)