Based on kernel version 3.19. Page generated on 2015-02-13 21:19 EST.
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 email@example.com 14 15 3) The Documentation/ portion of the patch should come in the series before 16 the code implementing the binding. 17 18 II. For kernel maintainers 19 20 1) If you aren't comfortable reviewing a given binding, reply to it and ask 21 the devicetree maintainers for guidance. This will help them prioritize 22 which ones to review and which ones are ok to let go. 23 24 2) For driver (not subsystem) bindings: If you are comfortable with the 25 binding, and it hasn't received an Acked-by from the devicetree 26 maintainers after a few weeks, go ahead and take it. 27 28 Subsystem bindings (anything affecting more than a single device) 29 then getting a devicetree maintainer to review it is required. 30 31 3) For a series going though multiple trees, the binding patch should be 32 kept with the driver using the binding. 33 34 III. Notes 35 36 0) Please see ...bindings/ABI.txt for details regarding devicetree ABI. 37 38 1) This document is intended as a general familiarization with the process as 39 decided at the 2013 Kernel Summit. When in doubt, the current word of the 40 devicetree maintainers overrules this document. In that situation, a patch 41 updating this document would be appreciated.