Searched refs:DO (Results 1 – 10 of 10) sorted by relevance
17 - DO attempt to make bindings complete even if a driver doesn't support some24 - DO use node names matching the class of the device. Many standard names are27 - DO check that the example matches the documentation especially after making42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible43 strings. DO use fallback compatibles when devices are the same as or a subset44 of prior implementations. DO add new compatibles in case there are new47 - DO use a vendor prefix on device specific property names. Consider if54 - DO use common property unit suffixes for properties with scientific units.57 - DO define properties in terms of constraints. How many entries? What are64 - DO put all MMIO devices under a bus node and not at the top-level.[all …]
18 # DO NOT ADD NEW PROPERTIES TO THIS LIST
25 # DO ACTUAL MODULE BUILDING
41 FOR %%f in (*.c) DO (
12 # GENERATED SOURCE CODE, DO NOT EDIT EXCEPT EXPERIMENTALLY #103 # GENERATED SOURCE CODE, DO NOT EDIT EXCEPT EXPERIMENTALLY #112 # GENERATED SOURCE CODE, DO NOT EDIT EXCEPT EXPERIMENTALLY #233 # GENERATED SOURCE CODE, DO NOT EDIT EXCEPT EXPERIMENTALLY #242 # GENERATED SOURCE CODE, DO NOT EDIT EXCEPT EXPERIMENTALLY #
15 PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected
119 - better scope control with DO block END.
29 DO NOT use a smaller "Speed Bin" than specified
2424 #define DO(which) \ in dump_dsl_dir() macro2428 DO(HEAD); in dump_dsl_dir()2429 DO(SNAP); in dump_dsl_dir()2430 DO(CHILD); in dump_dsl_dir()2431 DO(CHILD_RSRV); in dump_dsl_dir()2432 DO(REFRSRV); in dump_dsl_dir()2433 #undef DO in dump_dsl_dir()
318 APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO