Lines Matching full:your

1 How to Get Your Patch Accepted Into the Hwmon Subsystem
6 increase the chances of your change being accepted.
19 * Please run your patch through 'checkpatch --strict'. There should be no
27 * If your patch generates checkpatch errors, warnings, or check messages,
33 * Please test your patch thoroughly. We are not your test group.
39 * If your patch (or the driver) is affected by configuration options such as
52   your patch into a cleanup part and the actual addition. This makes it easier
53   to review your changes, and to bisect any resulting problems.
61 * Running your patch or driver file(s) through checkpatch does not mean its
62   formatting is clean. If unsure about formatting in your new driver, run it
88 * Limit the number of kernel log messages. In general, your driver should not
112   chips. If your chip lives at an address which can't be probed then the
120   Keep in mind that the chip might not be what your driver believes it is, and
124   completely initialize your chip and your driver first, then register with
127 * Use devm_hwmon_device_register_with_info() or, if your driver needs a remove
128   function, hwmon_device_register_with_info() to register your driver with the
132 * Your driver should be buildable as module. If not, please be prepared to
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