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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 25 Feb 2019 13:38:12 -0600
From:   Rob Herring <>
To:     Linus Walleij <>
Cc:     Jonathan Corbet <>,
        "H. Nikolaus Schaller" <>,
        Jonathan Cameron <>,
        Mark Rutland <>,
        Andy Shevchenko <>,
        Charles Keepax <>,
        Song Qiang <>,
        Jean-Baptiste Maneyrol <>,
        Martin Kelly <>,
        Jonathan Marek <>,
        Brian Masney <>,
        Stephan Gerhold <>,
        Discussions about the Letux Kernel 
        <>, Hartmut Knaack <>,
        Lars-Peter Clausen <>,
        Peter Meerwald-Stadler <>,
        "open list:IIO SUBSYSTEM AND DRIVERS" <>,
        "" <>,
        Gregor Boirie <>,
        Sebastian Reichel <>,
        Samu Onkalo <>
Subject: Re: [PATCH v2 02/10] iio: document bindings for mounting matrices

On Mon, Feb 25, 2019 at 12:24 PM Linus Walleij <> wrote:
> Hi Jon,
> On Mon, Feb 25, 2019 at 5:32 PM Jonathan Corbet <> wrote:
> > >  .../devicetree/bindings/iio/mount-matrix.txt  | 204 ++++++++++++++++++
> So this is a device tree binding.
> > So forgive me, but I have to ask: what are the chances of getting this
> > file in RST format?  It's 99% of the way there now, finishing the job
> > would allow it to be integrated into our docs tree.
> >
> > It should probably have an SPDX line too.
> The recent direction of the Device Tree bindings are not in the RST
> direction but in the direction of using another formal structure: YAML
> schemas.
> See e.g. Documentation/devicetree/bindings/example-schema.yaml
> The YAML schema makes it possible to verify device trees and examples
> inside the bindings to the specification using a context-free grammar.
> If we can join the RST and YAML ambitions is a good question. RST
> has nice typesetting properties, YAML has nice grammatic properties.

In fact there has been some experimentation there. The 'description'
portion of DT schema can be RST. And the rest being structured data
could be transformed to RST. Grant did some experiments there. The
idea being to generate the DT spec from schema (rather than integrate
into the kernel docs). But not much progress there and it's not
something I'm spending time on ATM.


Powered by blists - more mailing lists