Lines Matching refs:have

6 views on anybody, but this is what goes for anything that I have to be
26 how the indentation works if you have large indentations.
34 In short, 8-char indents make things easier to read, and have the added
59 Don't put multiple statements on a single line unless you have
116 However, there is one special case, namely functions: they have the
124 Heretic people all over the world have claimed that this inconsistency
153 25-line terminal screens here), you have more empty lines to put
253 have descriptive names, as do global functions. If you have a function
262 LOCAL variable names should be short, and to the point. If you have
268 If you are afraid to mix up your local variable names, you have another
297 The reason we have them for things like pte_t etc. is that there
354 complexity and indentation level of that function. So, if you have a
356 case-statement, where you have to do lots of small things for a lot of
357 different cases, it's OK to have a longer function.
359 However, if you have a complex function, and you suspect that a
365 than you would have done).
585 Data structures that have visibility outside the single-threaded
586 environment they are created and destroyed in should always have
592 users to have access to the data structure in parallel - and not having
601 Many data structures can indeed have two levels of reference counting,
611 have a reference count on it, you almost certainly have a bug.
689 Kernel messages do not have to be terminated with a period.
701 you have them, they can be a huge help for remote troubleshooting. However
709 Many subsystems have Kconfig debug options to turn on -DDEBUG in the
759 A reasonable rule of thumb is to not put inline at functions that have more
771 something it would have done anyway.
846 Do not include any of these in source files. People have their own personal
849 own custom mode, or may have some other magic method for making indentation
897 If you have a function or variable which may potentially go unused in a
914 references, etc). Thus, you still have to use an #ifdef if the code inside the