From 9061c0c9ab70bea29a56f1ea73f8f0f8859f0bab Mon Sep 17 00:00:00 2001 From: Sandrine Bailleux Date: Thu, 20 Aug 2020 10:41:36 +0200 Subject: [PATCH] doc: Minor formatting improvement in the coding guidelines document Change-Id: I5362780db422772fd547dc8e68e459109edccdd0 Signed-off-by: Sandrine Bailleux --- docs/process/coding-guidelines.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/process/coding-guidelines.rst b/docs/process/coding-guidelines.rst index f7d53a97e..97086047d 100644 --- a/docs/process/coding-guidelines.rst +++ b/docs/process/coding-guidelines.rst @@ -95,10 +95,13 @@ By default, all logging statements with a log level ``<= LOG_LEVEL_INFO`` will be compiled into debug builds and all statements with a log level ``<= LOG_LEVEL_NOTICE`` will be compiled into release builds. This can be overridden from the command line or by the platform makefile (although it may be -necessary to clean the build directory first). For example, to enable -``VERBOSE`` logging on FVP: +necessary to clean the build directory first). -``make PLAT=fvp LOG_LEVEL=50 all`` +For example, to enable ``VERBOSE`` logging on FVP: + +.. code:: shell + + make PLAT=fvp LOG_LEVEL=50 all Use const data where possible ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^