|author||Joel Sherrill <email@example.com>||2016-10-28 15:56:19 -0500|
|committer||Joel Sherrill <firstname.lastname@example.org>||2016-10-28 15:56:19 -0500|
|parent||cpu_supplement: Fixed numbered list (diff)|
c_user: Fix numbered lists.
Diffstat (limited to '')
2 files changed, 5 insertions, 5 deletions
diff --git a/c_user/configuring_a_system.rst b/c_user/configuring_a_system.rst
index fdd255a..9c36b2d 100644
@@ -4127,9 +4127,9 @@ clusters. Clusters with a cardinality of one are partitions. Each cluster is
owned by exactly one scheduler instance. In order to use clustered scheduling
the application designer has to answer two questions.
-# How is the set of processors partitioned into clusters?
+#. How is the set of processors partitioned into clusters?
-# Which scheduler is used for which cluster?
+#. Which scheduler is used for which cluster?
diff --git a/c_user/pci_library.rst b/c_user/pci_library.rst
index 0d95f3e..6bc5988 100644
@@ -113,11 +113,11 @@ peripherals to access one another using Memory or I/O accesses and that
interrupts are properly handled. Three different spaces are defined and mapped
-# I/O space (IO)
+#. I/O space (IO)
-# non-prefetchable Memory space (MEMIO)
+#. non-prefetchable Memory space (MEMIO)
-# prefetchable Memory space (MEM)
+#. prefetchable Memory space (MEM)
Regions of the same type (I/O or Memory) may not overlap which is guaranteed by
the software. MEM regions may be mapped into MEMIO regions, but MEMIO regions