michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: fix 'bullet list' formatting errors

Browse source 
Change-Id: I2114052d1cee68845c74c0c1a89a75bea14cd312
Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
This commit is contained in:
Inaky Perez-Gonzalez 2016-06-13 11:45:26 -07:00 • committed by Anas Nashif
commit eb5172c72d
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/board/em_starterkit.rst
View file

@ -156,7 +156,7 @@ On your development environment, you will need to:
* Open a serial port emulator (i.e. on Linux minicom, putty, screen, etc)
* Specify the tty driver name, for example, on Linux this may be
:file:`/dev/ttyUSB1`
:file:`/dev/ttyUSB1`
* Set the communication settings to:

8
doc/reference/kbuild/kbuild_project.rst
View file

@ -38,7 +38,7 @@ A common application project is composed of the following files:
different directory.
* **Makefile**: Adds the developer's source code into the build system's
recursion model.
recursion model.
The application's source code can be organized in subdirectories.
Each directory must follow the Kbuild Makefile conventions; see
@ -130,9 +130,9 @@ QEMU is the supported emulation system of the kernel. QEMU must be invoked
with the -s and -S options.
* :option:`-S` Do not start CPU at startup; rather, you must type 'c' in the
monitor.
monitor.
* :option:`-s` Shorthand for :literal:`-gdb tcp::1234`: open a GDB server on
TCP port 1234.
TCP port 1234.
The build system can build the elf binary and call the QEMU process with
the :makevar:`qemu` target. The QEMU debug options can be set using the
@ -202,4 +202,4 @@ elf binary file, in this instance, the :file:`zephyr.elf` file.
Both commands execute the :abbr:`gdb (GNU Debugger)`.
The command name might change depending on the toolchain you are using
and your cross-development tools.
and your cross-development tools.

2
doc/subsystems/power_management.rst
View file

@ -542,7 +542,7 @@ operations:
#. The PMA returns the :code:`SYS_PM_LOW_POWER_STATE` code.
* If the time allotted is not enough for the :code:`SYS_PM_LOW_POWER_STATE`
policy, the PMA returns the :code:`SYS_PM_DEVICE_SUSPEND_ONLY` code.
policy, the PMA returns the :code:`SYS_PM_DEVICE_SUSPEND_ONLY` code.
When a device fails to suspend, the PMA executes the following operations: