Lines Matching refs:that

4 Here are some basic things that developers should do if they want to see their
7 These are all above and beyond the documentation that is provided in
12 1: If you use a facility then #include the file that defines/declares
13    that facility.  Don't depend on other header files pulling in ones
14    that you use.
32    You should be able to justify all violations that remain in
46     that they find.  Note: checkstack does not point out problems explicitly,
47     but any one function that uses more than 512 bytes on the stack is a
76     Patches that change userspace interfaces should be CCed to
79 20: Check that it all passes `make headers_check'.
92     that it still works with all of the other queued patches and various
96     source code that explains the logic of what they are doing and why.
102     APIs or features that are related to the following kconfig symbols,
104     and/or =m (if that option is available) [not all of these at the