[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1776429.KtRq374vTa@phil>
Date: Thu, 31 Mar 2016 19:15:43 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: Andreas Färber <afaerber@...e.de>
Cc: linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>
Subject: Re: [PATCH v4 1/8] arm64: dts: rockchip: Clean up /memory nodes
Am Samstag, 19. März 2016, 09:04:08 schrieb Heiko Stuebner:
> Am Mittwoch, 16. März 2016, 14:58:39 schrieb Andreas Färber:
> > A dtc update results in warnings for nodes with reg property but without
> > unit address in the node name, so rename /memory to /memory@0.
> >
> > Signed-off-by: Andreas Färber <afaerber@...e.de>
>
> applied to a dts64-fixes branch for 4.6, after changing the commit message
> to ----
> A dtc update results in warnings for nodes with reg property but without
> unit address in the node name, so rename /memory to /memory@...rtaddress
> (memory starts at 0 in the case of the rk3368).
> ----
>
> To clarify that the @0 is not arbitary chosen.
This dtc update in question hasn't landed in v4.6-rc1 and from what I
gathered will need some changes. The patch is obviously still correct, but I
have now moved it from v4.6-fixes to the regular v4.7 64bit dts changes.
Heiko
Powered by blists - more mailing lists