linux-kernel - Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers

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]

Date:   Sun, 28 Aug 2016 15:36:11 -0500
From:   Timur Tabi <timur@...i.org>
To:     Sebastian Frias <sf84@...oste.net>
Cc:     devicetree <devicetree@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Mason <slash.tmp@...e.fr>
Subject: Re: ARM,SoC: About the use DT-defined properties by 3rd-party drivers

On Wed, Aug 24, 2016 at 9:29 AM, Sebastian Frias <sf84@...oste.net> wrote:
>
> If this is really not possible, it forces the SoC manufacturer to expose
> those properties in a different way, thus wasting a (seemingly) perfectly
> fine way of doing so: the DT and its documentation.

When you submit a new driver upstream, that patch also includes the
new device tree nodes and documentation for those nodes.  Everything
is peer-reviewed together.  I don't understand what you think the
problem is.