diff options
| author | Joel Sherrill <joel@rtems.org> | 2016-10-27 19:47:07 -0500 |
|---|---|---|
| committer | Joel Sherrill <joel@rtems.org> | 2016-10-27 19:47:07 -0500 |
| commit | 36def9125c9adf4049a18105d48715ac8606e1ec (patch) | |
| tree | b9a3c06d3fad69f3213474d5d16d844b862cc268 /porting/priority_bitmap.rst | |
| parent | initilization_code.rst: Fix figure formatting (diff) | |
| download | rtems-docs-36def9125c9adf4049a18105d48715ac8606e1ec.tar.bz2 | |
rtems-docs: Fix many unnecessary back slashes
Diffstat (limited to '')
| -rw-r--r-- | porting/priority_bitmap.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/porting/priority_bitmap.rst b/porting/priority_bitmap.rst index d546f8f..4ce89cb 100644 --- a/porting/priority_bitmap.rst +++ b/porting/priority_bitmap.rst @@ -56,9 +56,9 @@ The _CPU_Bitfield_Find_first_bit routine sets _output to the bit number of the first bit set in ``_value``. ``_value`` is of CPU dependent type``Priority_bit_map_Control``. A stub version of this routine is as follows: .. code:: c - #define _CPU_Bitfield_Find_first_bit( _value, _output ) \\ - { \\ - (_output) = 0; /* do something to prevent warnings \*/ \\ + #define _CPU_Bitfield_Find_first_bit( _value, _output ) \ + { \ + (_output) = 0; /* do something to prevent warnings */ \ } There are a number of variables in using a "find first bit" type @@ -129,9 +129,9 @@ something like this stub example did: .. code:: c #if (CPU_USE_GENERIC_BITFIELD_CODE == FALSE) - #define _CPU_Bitfield_Find_first_bit( _value, _output ) \\ - { \\ - (_output) = 0; /* do something to prevent warnings \*/ \\ + #define _CPU_Bitfield_Find_first_bit( _value, _output ) \ + { \ + (_output) = 0; /* do something to prevent warnings */ \ } #endif |