path: root/dts/Bindings/submitting-patches.txt
diff options
authorSascha Hauer <>2014-04-25 11:22:32 +0200
committerSascha Hauer <>2014-04-28 09:08:46 +0200
commit00ce25c6dcdae5582ae4be37147ab33678adc995 (patch)
tree41c93102ae304a61738c31353e3cb5336ef0b297 /dts/Bindings/submitting-patches.txt
parent0af79fbb6779921d3f1962773adb7fb57d3c89d4 (diff)
Add devicetree source files as of Linux-3.15-rc2
This adds the Linux dts files to barebox. The dts files are generated from Ian Campbells device-tree-rebasing.git: git:// The dts are found in dts/ in the barebox repository and will be updated from upstream regularly, probably for each upstream -rc. To keep the synchronization with upstream easy no changes to the original files are allowed under dts/. Instead changes to upstream dts files will be done using overlays in arch/$ARCH/dts/. Signed-off-by: Sascha Hauer <>
Diffstat (limited to 'dts/Bindings/submitting-patches.txt')
1 files changed, 38 insertions, 0 deletions
diff --git a/dts/Bindings/submitting-patches.txt b/dts/Bindings/submitting-patches.txt
new file mode 100644
index 0000000..042a027
--- /dev/null
+++ b/dts/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
+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.