[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201201182231.GL2073444@lunn.ch>
Date: Tue, 1 Dec 2020 19:22:31 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: Aryan Srivastava <Aryan.Srivastava@...iedtelesis.co.nz>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"gregory.clement@...tlin.com" <gregory.clement@...tlin.com>,
"sebastian.hesselbarth@...il.com" <sebastian.hesselbarth@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: mvebu: Add device tree for ATL-x530 Board
> This is what we've done in our kernel fork. But for upstreaming we
> wanted to start slow and maybe move things into one or more common .dtsi
> files if/when needed (in particular there are some models in development
> now that use different i2c mux and hwmon chips).
O.K. It is not particularly disruptive to refactor later, so lets
start with this.
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists