Grant, On Tue, Jan 21, 2014 at 02:40:48PM +0000, Grant Likely wrote: > Hi everyone, > > Today on the devicetree conf call Sorry I couldn't make it, I had a last minute engagement yesterday AM. > we (Rob, Ian and I) talked about culling the volume of traffic on the > devicetree list so that it would be more useful to the DTC maintainers > and non-Linux users like freebsd. We'd like to propose creating the > following two lists so that those interested don't need to drink from > the firehose: > > devicetree-compiler: Specifically for discussing dt tooling topics > (parsing, schema validation, data format) Ack. > devicetree-spec: For discussing 'core' device tree bindings. ie. > anything that would be a candidate for putting into an ePAPR type > spec. Individual device bindings would continue to be posted to > devicetree@xxxxxxxxxxxxxxx, but anything affecting subsystems or > generic patterns should be posted to this new list. > > Thoughts? How do patch series submitters easily determine when to send to -spec vice the general list? I'm thinking wrt get_maintainers.pl. Perhaps it's worth considering organizing Doc.../bindings/ into subsystem/ and ...'not'? The "suitable for ePAPR" criteria would be a good differentiator. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
