diff options
author | Jason Cooper <jason@lakedaemon.net> | 2013-12-17 16:59:40 +0000 |
---|---|---|
committer | Grant Likely <grant.likely@linaro.org> | 2014-01-20 22:31:06 +0000 |
commit | 2a9330010bea5982a5c6593824bc036bf62d67b7 (patch) | |
tree | 6e3658433e3bde5b01aff49ab382fc5b74290942 /Documentation/devicetree/bindings/submitting-patches.txt | |
parent | 42ccd781bb206804501ff490fd771bb940ca9969 (diff) |
dt/bindings: submitting patches and ABI documents
Add some guidance documentation about what to do with device tree
bindings and how ABI stability is to be handled.
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
[grant.likely: added some clarification on subsystem binding rules]
Signed-off-by: Grant Likely <grant.likely@linaro.org>
Diffstat (limited to 'Documentation/devicetree/bindings/submitting-patches.txt')
-rw-r--r-- | Documentation/devicetree/bindings/submitting-patches.txt | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/submitting-patches.txt b/Documentation/devicetree/bindings/submitting-patches.txt new file mode 100644 index 000000000000..042a0273b8ba --- /dev/null +++ b/Documentation/devicetree/bindings/submitting-patches.txt @@ -0,0 +1,38 @@ + + Submitting devicetree (DT) binding patches + +I. For patch submitters + + 0) Normal patch submission rules from Documentation/SubmittingPatches + applies. + + 1) The Documentation/ portion of the patch should be a separate patch. + + 2) Submit the entire series to the devicetree mailinglist at + + devicetree@vger.kernel.org + +II. For kernel maintainers + + 1) If you aren't comfortable reviewing a given binding, reply to it and ask + the devicetree maintainers for guidance. This will help them prioritize + which ones to review and which ones are ok to let go. + + 2) For driver (not subsystem) bindings: If you are comfortable with the + binding, and it hasn't received an Acked-by from the devicetree + maintainers after a few weeks, go ahead and take it. + + Subsystem bindings (anything affecting more than a single device) + then getting a devicetree maintainer to review it is required. + + 3) For a series going though multiple trees, the binding patch should be + kept with the driver using the binding. + +III. Notes + + 0) Please see ...bindings/ABI.txt for details regarding devicetree ABI. + + 1) This document is intended as a general familiarization with the process as + decided at the 2013 Kernel Summit. When in doubt, the current word of the + devicetree maintainers overrules this document. In that situation, a patch + updating this document would be appreciated. |