linux-kernel - Re: [Patch v4 9/9] arm64: Update device tree for Layerscape SoCs

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, 29 Aug 2016 14:39:21 -0700
From:   Olof Johansson <olof@...om.net>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Shawn Guo <shawnguo@...nel.org>, York Sun <york.sun@....com>,
        Mark Rutland <mark.rutland@....com>,
        yangbo lu <yangbo.lu@...escale.com>,
        Liu Gang <Gang.Liu@....com>, morbidrsa@...il.com,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Arnd Bergmann <arnd@...db.de>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Bhupesh Sharma <bhupesh.sharma@...escale.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will.deacon@....com>, stuart.yoder@....com,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        oss@...error.net, Rob Herring <robh+dt@...nel.org>,
        Rajesh Bhagat <rajesh.bhagat@...escale.com>,
        Mingkai Hu <Mingkai.Hu@...escale.com>,
        Li Yang <leoli@...escale.com>, Yuan Yao <yao.yuan@....com>,
        linux-edac@...r.kernel.org
Subject: Re: [Patch v4 9/9] arm64: Update device tree for Layerscape SoCs

On Mon, Aug 29, 2016 at 1:05 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Mon, Aug 29, 2016 at 02:34:48PM +0800, Shawn Guo wrote:
>> Is it mandatory to have DTS changes go with driver part altogether?
>
> Yes, because the EDAC driver needs them to even load properly.
>
>> Otherwise, I prefer to have them go through separate tree.
>
> Any particular reason why you prefer that?
>
> We've been doing this for other ARM EDAC drivers already and there were
> no issues whatsoever.

DT changes need to go through arm-soc. It's how we've been operating
for several years now.

It can be a huge pain when DT patches get merged through driver trees
and others are also modifying those files. Don't do it. You don't know
if someone else out there is changing these files, that's why we have
maintainers who own them and coordinate the changes.


If there are special circumstances such that the DT contents has to go
in with the same tree, then we can consider alternatives. But I can't
remember having one of those situations for quite a while now.


-Olof