linux-kernel - Re: [PATCH v2 1/4] dt-bindings: Document how Chromebooks with depthcharge boot

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:   Mon, 16 May 2022 17:11:21 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Doug Anderson <dianders@...omium.org>
Cc:     Rob Herring <robh@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Stephen Boyd <swboyd@...omium.org>,
        Matthias Kaehlcke <mka@...omium.org>,
        Rajendra Nayak <quic_rjendra@...cinc.com>,
        Alexandru M Stan <amstan@...omium.org>,
        Julius Werner <jwerner@...omium.org>,
        "Joseph S . Barrera III" <joebar@...omium.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: Document how Chromebooks with
 depthcharge boot

On 16/05/2022 17:06, Doug Anderson wrote:
>>
>> This is not a Devicetree (generic) document, so it is not the best place
>> for it. Maybe regular vendor place, e.g . Documentation/arm/google/ ?
> 
> I can put it there. ...but taking your two pieces of advice together,
> you're saying:
> 
> 1. Don't add this under the devicetree directory.
> 
> 2. Don't refer to this by URL but instead by a relative file path.
> 
> I can do both of those two things, but I always had it in my mind that
> the device tree was supposed to be "Linux agnostic". In other words,
> you could refer to Linux as one OS that boots with device tree, but I
> thought that the device tree docs were supposed to stand on their own.
> With the above two suggestions, it seems like an extra piece tieing
> the two together and assuming that both Linux and device tree docs are
> living in the same place.

D'oh, you are right, it should not be referenced via path, if moved into
docs. Then let's discard that part of idea, so just move it to
Documentation/arm/google/ and keep the URL link in your bindings change.


Best regards,
Krzysztof