| Jason Cooper | 2a93300 | 2013-12-17 16:59:40 +0000 | [diff] [blame] | 1 | |
| 2 | Submitting devicetree (DT) binding patches |
| 3 | |
| 4 | I. For patch submitters |
| 5 | |
| 6 | 0) Normal patch submission rules from Documentation/SubmittingPatches |
| 7 | applies. |
| 8 | |
| 9 | 1) The Documentation/ portion of the patch should be a separate patch. |
| 10 | |
| 11 | 2) Submit the entire series to the devicetree mailinglist at |
| 12 | |
| 13 | devicetree@vger.kernel.org |
| 14 | |
| 15 | II. For kernel maintainers |
| 16 | |
| 17 | 1) If you aren't comfortable reviewing a given binding, reply to it and ask |
| 18 | the devicetree maintainers for guidance. This will help them prioritize |
| 19 | which ones to review and which ones are ok to let go. |
| 20 | |
| 21 | 2) For driver (not subsystem) bindings: If you are comfortable with the |
| 22 | binding, and it hasn't received an Acked-by from the devicetree |
| 23 | maintainers after a few weeks, go ahead and take it. |
| 24 | |
| 25 | Subsystem bindings (anything affecting more than a single device) |
| 26 | then getting a devicetree maintainer to review it is required. |
| 27 | |
| 28 | 3) For a series going though multiple trees, the binding patch should be |
| 29 | kept with the driver using the binding. |
| 30 | |
| 31 | III. Notes |
| 32 | |
| 33 | 0) Please see ...bindings/ABI.txt for details regarding devicetree ABI. |
| 34 | |
| 35 | 1) This document is intended as a general familiarization with the process as |
| 36 | decided at the 2013 Kernel Summit. When in doubt, the current word of the |
| 37 | devicetree maintainers overrules this document. In that situation, a patch |
| 38 | updating this document would be appreciated. |