doc: remove warning on failed code highlighting
Four code snippets fail to be properly recognized by the code highlighter; the makefile snippets seem to be because of the $ character (and I have found a way to escape it out). The C code, I haven't been able to find out why. Killed the warning by setting the code-block style to 'none' on all of them. It is not the best sollution, but it beats a polluted build process. Change-Id: I8fa7d327354a93bacad40e25596c9dbaf9ea1e92 Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
This commit is contained in:
parent
e03babf7d0
commit
bf94c8f3b3
2 changed files with 17 additions and 17 deletions
|
@ -134,15 +134,15 @@ This code waits up to 5 ticks for an 80 byte memory block to become
|
|||
available and gives a warning if a suitable memory block is not obtained
|
||||
in that time.
|
||||
|
||||
.. code-block:: c
|
||||
.. code-block:: none
|
||||
|
||||
struct k_block block;
|
||||
struct k_block block;
|
||||
|
||||
if (task_mem_pool_alloc(&block, MYPOOL, 80, 5) == RC_OK) {
|
||||
/* use memory block */
|
||||
} else {
|
||||
printf('Memory allocation timeout');
|
||||
}
|
||||
if (task_mem_pool_alloc(:&block, MYPOOL, 80, 5) == RC_OK) {
|
||||
/* use memory block */
|
||||
} else {
|
||||
printf('Memory allocation timeout');
|
||||
}
|
||||
|
||||
Example: Requesting a Memory Block from a Pool with a No-Blocking Condition
|
||||
===========================================================================
|
||||
|
@ -150,15 +150,15 @@ Example: Requesting a Memory Block from a Pool with a No-Blocking Condition
|
|||
This code gives an immediate warning when it can not satisfy the request for
|
||||
a memory block of 80 bytes.
|
||||
|
||||
.. code-block:: c
|
||||
.. code-block:: none
|
||||
|
||||
struct k_block block;
|
||||
struct k_block block;
|
||||
|
||||
if (task_mem_pool_alloc (&block, MYPOOL, 80, TICKS_NONE) == RC_OK) {
|
||||
/* use memory block */
|
||||
} else {
|
||||
printf('Memory allocation timeout');
|
||||
}
|
||||
if (task_mem_pool_alloc (&block, MYPOOL, 80, TICKS_NONE) == RC_OK) {
|
||||
/* use memory block */
|
||||
} else {
|
||||
printf('Memory allocation timeout');
|
||||
}
|
||||
|
||||
Example: Freeing a Memory Block Back to a Pool
|
||||
==============================================
|
||||
|
|
|
@ -63,7 +63,7 @@ example, if the option :option:`CONFIG_VAR` is set and it implies that a source
|
|||
file must be added in the compilation process, then the following line adds the
|
||||
source code conditionally:
|
||||
|
||||
.. code-block:: make
|
||||
.. code-block:: none
|
||||
|
||||
obj-$(CONFIG_VAR) += <file>.o
|
||||
|
||||
|
@ -88,9 +88,9 @@ an additional lever of recursion.
|
|||
|
||||
Directories can also be conditionally added:
|
||||
|
||||
.. code-block:: make
|
||||
.. code-block:: none
|
||||
|
||||
oby-$(CONFIG_VAR) += <directory_name>/
|
||||
obj-y-$(CONFIG_VAR) += <directory_name>/
|
||||
|
||||
The subdirectory must contain its own Makefile following the rules described in
|
||||
:ref:`makefile_conventions`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue