[Ksummit-2013-discuss] [ATTEND] Handling of devicetree bindings

Mark Brown broonie at sirena.org.uk
Tue Jul 16 05:58:48 EST 2013


On Mon, Jul 15, 2013 at 11:41:57AM -0700, Greg KH wrote:
> On Mon, Jul 15, 2013 at 06:06:00PM +0100, Mark Brown wrote:

> > At the minute it's about at the level of saying that if you're not sure
> > or don't know you should get the devicetree-discuss mailing list to
> > review it.  Ideally someone would write that document, though I wouldn't
> > hold my breath and there is a bunch of convention involved.

> So, what should I, as a subsystem maintainer, do if I get a patch with a
> binding in it?  Wait some random amount of time before I can just apply
> it because no one on the mailing list said anything about it?  Trust the
> developer who wrote it?  Or just reject them all?

> What do you advise?

Right, this is the problem.  Given that this is supposed to be about
defining an ABI probably sit on it until someone with more DT experience
turns up to help though obviously that isn't always constructive.
Trying to figure things out enough to decide if it's sane is another
option, as is helping the submitter make their binding easier to review
by doing things like split out more complex elements into incremental
additions or making sure they aren't deluging the DT list with lots of
subsystem stuff other than bindings.

Ideally a lot of this stuff will be fairly standard for the subsystem so
hopefully it'll very quickly become apparent what's unusual which will
help a lot.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/devicetree-discuss/attachments/20130715/8d3b4ec8/attachment.sig>


More information about the devicetree-discuss mailing list