Lines Matching full:not

23 * Please use the standard multi-line comment style. Do not mix C and C++
33 * Please test your patch thoroughly. We are not your test group.
34   Sometimes a patch can not or not completely be tested because of missing
36   architecture. If run-time testing was not achieved, it should be written
61 * Running your patch or driver file(s) through checkpatch does not mean its
63   through Lindent. Lindent is not perfect, and you may have to do some minor
80 * Avoid macros to generate groups of sensor attributes. It not only confuses
88 * Limit the number of kernel log messages. In general, your driver should not
91   that kernel error log messages not only fill up the kernel log, but also are
97   If a function is not supported by devres, consider using devm_add_action().
101   must not print messages such as "Chip XXX not found/supported".
105   pollute the kernel log and not provide any value.
120   Keep in mind that the chip might not be what your driver believes it is, and
130   possible. Do not use hwmon_device_register().
132 * Your driver should be buildable as module. If not, please be prepared to
135 * Do not provide support for deprecated sysfs attributes.
137 * Do not create non-standard attributes unless really needed. If you have to use
144   capabilities. While we do not expect your driver to support everything the
147 * Last but not least, please check if a driver for your chip already exists