summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/submitting-patches.txt
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier.martinez@collabora.co.uk>2014-10-09 20:24:07 +0200
committerJonathan Corbet <corbet@lwn.net>2014-10-21 10:31:27 -0400
commitef0b97e3daeabf3bf39bc9ddf7d9f7207b90d91b (patch)
treea4838affe26d3d6d0aacc5012b74ee34ae2494eb /Documentation/devicetree/bindings/submitting-patches.txt
parentdce9b2c91495d37e5a6a976277a408f42da56a70 (diff)
Documentation: dt-bindings: Explain order in patch series
When posting a patch series that includes both code implementing a Device Tree binding and its associated documentation, the DT docs should come in the series before the implementation. This not only avoids checkpatch.pl to complain about undocumented bindings but also makes the review process easier. Document this convention since it may not be obvious. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/devicetree/bindings/submitting-patches.txt')
-rw-r--r--Documentation/devicetree/bindings/submitting-patches.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/submitting-patches.txt b/Documentation/devicetree/bindings/submitting-patches.txt
index 042a0273b8ba..b7ba01ad1426 100644
--- a/Documentation/devicetree/bindings/submitting-patches.txt
+++ b/Documentation/devicetree/bindings/submitting-patches.txt
@@ -12,6 +12,9 @@ I. For patch submitters
devicetree@vger.kernel.org
+ 3) The Documentation/ portion of the patch should come in the series before
+ the code implementing the binding.
+
II. For kernel maintainers
1) If you aren't comfortable reviewing a given binding, reply to it and ask