Difference between revisions of "Device tree history"
(Fix formatting. Add section: The bindings fire hose is clogged) |
(→The bindings fire hose is clogged: add the word "review" to the section title) |
||
Line 14: | Line 14: | ||
:http://lkml.indiana.edu/hypermail/linux/kernel/0905.3/02304.html | :http://lkml.indiana.edu/hypermail/linux/kernel/0905.3/02304.html | ||
− | == The bindings fire hose is clogged == | + | == The bindings review fire hose is clogged == |
Discussion at the 2013 Kernel Summit led to the creation of the kernel file | Discussion at the 2013 Kernel Summit led to the creation of the kernel file |
Revision as of 20:13, 18 June 2015
Mailing list discussion
"Recent" (2009) discussion of "Flattened Device Tree" work on linux-embedded mailing list:
Russell King is against adding support for FDT to the ARM platform (see whole thread for interesting discussion):
But maybe Russell can be convinced:
David Gibson defends FDT:
The bindings review fire hose is clogged
Discussion at the 2013 Kernel Summit led to the creation of the kernel file Documentation/devicetree/bindings/submitting-patches.txt, including the following note:
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.