Lines Matching full:code

32 the code move too far to the right, and makes it hard to read on a
45 .. code-block:: c
67 .. code-block:: c
107 .. code-block:: c
116 .. code-block:: c
132 .. code-block:: c
149 .. code-block:: c
157 .. code-block:: c
177 .. code-block:: c
184 .. code-block:: none
194 .. code-block:: c
205 .. code-block:: c
228 .. code-block:: c
236 .. code-block:: c
245 .. code-block:: c
273 appropriate, so you can start typing the next line of code right away.
275 putting a line of code there, such as if you leave a blank line.  As a result,
324 .. code-block:: c
332 .. code-block:: c
382      permitted -- although they are not mandatory in new code of your
385      When editing existing code which already uses one or the other set
386      of types, you should conform to the existing choices in that code.
434 .. code-block:: c
472 - saves the compiler work to optimize redundant code away ;)
474 .. code-block:: c
500 .. code-block:: c
507 The bug in this code is that on some exit paths ``foo`` is NULL.  Normally the
511 .. code-block:: c
526 try to explain HOW your code works in a comment: it's much better to
527 write the code so that the **working** is obvious, and it's a waste of
528 time to explain badly written code.
530 Generally, you want your comments to tell WHAT your code does, not HOW.
545 .. code-block:: c
549 	 * comments in the Linux kernel source code.
559 .. code-block:: c
587 .. code-block:: none
655 these rules, to quickly re-format parts of your code automatically,
718 filesystem code (``struct super_block``: s_count and s_active).
729 .. code-block:: c
742 .. code-block:: c
754 .. code-block:: c
763 function; don't break the internal parsers of those who will read the code.
767 .. code-block:: c
772 code and it's prone to breakage from seemingly innocent changes.
781 .. code-block:: c
789 .. code-block:: c
851 .. code-block:: c
865 .. code-block:: c
871 .. code-block:: c
896 than 3 lines of code in them. An exception to this rule are the cases where
915 failed.  Such a value can be represented as an error-code integer
926 	the function should return an error-code integer.  If the name
983 .. code-block:: c
989 .. code-block:: c
995 defined that you shouldn't reproduce in your code.
1005 .. code-block:: c
1011 .. code-block:: c
1021 .. code-block:: c
1035 In architecture-specific code, you may need to use inline assembly to interface
1057 .. code-block:: c
1068 files; doing so makes code harder to read and logic harder to follow.  Instead,
1072 any code for the stub calls, producing identical results, but the logic will
1086 Within code, where possible, use the IS_ENABLED macro to convert a Kconfig
1089 .. code-block:: c
1096 the block of code just as with an #ifdef, so this will not add any runtime
1097 overhead.  However, this approach still allows the C compiler to see the code
1099 references, etc).  Thus, you still have to use an #ifdef if the code inside the
1106 .. code-block:: c