linux-kernel - Re: The future of DT binding maintainership

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1307250043080.24195@nftneq.ynat.uz>
Date:	Thu, 25 Jul 2013 00:47:08 -0700 (PDT)
From:	David Lang <david@...g.hm>
To:	Grant Likely <grant.likely@...retlab.ca>
cc:	Tomasz Figa <tomasz.figa@...il.com>,
	Wolfram Sang <w.sang@...gutronix.de>,
	Mark Rutland <mark.rutland@....com>,
	Stephen Warren <swarren@...dotorg.org>,
	Ian Campbell <ian.campbell@...rix.com>,
	Pawel Moll <pawel.moll@....com>, devicetree@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	Rob Herring <rob.herring@...xeda.com>,
	Olof Johansson <olof@...om.net>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: The future of DT binding maintainership

On Wed, 24 Jul 2013, Grant Likely wrote:

> I wouldn't get to hung up about trying to reuse the same file format as
> the .dts files. Most of the bindings are going to be very flat in
> nature, and schemas need to be expresive in a different way from the
> .dts files themselves.
>
> We'll want to have an easy way to define trivial bindings. There are a
> lot of devices that only define a new 'compatible' string, but they
> don't actually require anything more than reg and interrupts. Can we
> maybe have a schema file that lists trivial bindings?

It sounds like a log of the bindings will really consist of something similar to 
"take this other binding definition and change these values"

I think that figuring out a good way to handle this (and make sure that when 
people change one binding, they can know what other bindings they are changing 
through the dependancies) is at least as important as figuring out the formal 
schemas and multiple inheritance issues.

David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/