Lines Matching +full:check +full:- +full:patch
1 How to Get Your Patch Accepted Into the Hwmon Subsystem
10 ----------
14 - Documentation/process/submit-checklist.rst
15 - Documentation/process/submitting-drivers.rst
16 - Documentation/process/submitting-patches.rst
17 - Documentation/process/coding-style.rst
19 * Please run your patch through 'checkpatch --strict'. There should be no
20 errors, no warnings, and few if any check messages. If there are any
23 * Please use the standard multi-line comment style. Do not mix C and C++
27 * If your patch generates checkpatch errors, warnings, or check messages,
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
35 hardware. In such cases, you should test-build the code on at least one
36 architecture. If run-time testing was not achieved, it should be written
37 explicitly below the patch header.
39 * If your patch (or the driver) is affected by configuration options such as
44 -------------------------------------------
52 your patch into a cleanup part and the actual addition. This makes it easier
55 * Never mix bug fixes, cleanup, and functional enhancements in a single patch.
59 --------------
61 * Running your patch or driver file(s) through checkpatch does not mean its
83 * Avoid calculations in macros and macro-generated functions. While such macros
96 and supported functions, please see Documentation/driver-api/driver-model/devres.rst.
109 * Only the following I2C addresses shall be probed: 0x18-0x1f, 0x28-0x2f,
110 0x48-0x4f, 0x58, 0x5c, 0x73 and 0x77. Probing other addresses is strongly
111 discouraged as it is known to cause trouble with other (non-hwmon) I2C
137 * Do not create non-standard attributes unless really needed. If you have to use
138 non-standard attributes, or you believe you do, discuss it on the mailing list
140 non-standard attribute(s).
141 Standard attributes are specified in Documentation/hwmon/sysfs-interface.rst.
147 * Last but not least, please check if a driver for your chip already exists