[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160829080530.GA25468@nazgul.tnic>
Date: Mon, 29 Aug 2016 10:05:30 +0200
From: Borislav Petkov <bp@...en8.de>
To: Shawn Guo <shawnguo@...nel.org>
Cc: 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,
Arnd Bergmann <arnd@...db.de>, 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, oss@...error.net,
Rob Herring <robh+dt@...nel.org>,
Rajesh Bhagat <rajesh.bhagat@...escale.com>,
Olof Johansson <olof@...om.net>,
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 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.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
Powered by blists - more mailing lists