Lines Matching full:if

20   errors, no warnings, and few if any check messages. If there are any
27 * If your patch generates checkpatch errors, warnings, or check messages,
36   architecture. If run-time testing was not achieved, it should be written
39 * If your patch (or the driver) is affected by configuration options such as
51 * If the added functionality requires some cleanup or structural changes, split
62   formatting is clean. If unsure about formatting in your new driver, run it
78 * Avoid forward declarations if you can. Rearrange the code if necessary.
97   If a function is not supported by devres, consider using devm_add_action().
99 * If the driver has a detect function, make sure it is silent. Debug messages
104   address if a chip is detected on that address. Unnecessary messages will just
107 * Provide a detect function if and only if a chip can be detected reliably.
112   chips. If your chip lives at an address which can't be probed then the
116 * Avoid writing to chip registers in the detect function. If you have to write,
127 * Use devm_hwmon_device_register_with_info() or, if your driver needs a remove
129   hwmon subsystem. Try using devm_add_action() instead of a remove function if
132 * Your driver should be buildable as module. If not, please be prepared to
137 * Do not create non-standard attributes unless really needed. If you have to use
147 * Last but not least, please check if a driver for your chip already exists