From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Norris Subject: Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs Date: Mon, 20 Mar 2017 16:07:48 -0700 Message-ID: <20170320230748.GA97915@google.com> References: <20170210010521.78872-1-briannorris@chromium.org> <20170210010521.78872-2-briannorris@chromium.org> <1529949.5djtX72aeJ@phil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1529949.5djtX72aeJ@phil> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Heiko Stuebner Cc: Olof Johansson , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Doug Anderson , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "open list:ARM/Rockchip SoC..." , Rob Herring , Chris Zhong , Stephen Barber , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Caesar Wang List-Id: devicetree@vger.kernel.org In case this thread is easier to notice... Olof, On Mon, Feb 27, 2017 at 07:20:48PM +0100, Heiko Stuebner wrote: > Am Dienstag, 21. Februar 2017, 15:47:31 CET schrieb Olof Johansson: > > On Thu, Feb 9, 2017 at 5:05 PM, Brian Norris wrote: > > > From: Douglas Anderson > > > > > > We'd like to be able to use the cros-ec-keyboard.dtsi and > > > cros-ec-sbs.dtsi snippets for arm64 devices. Currently those files live > > > in the arm/boot/dts directory. > > > > > > Let's follow the convention set by commit 8ee57b8182c4 ("ARM64: dts: > > > vexpress: Use a symlink to vexpress-v2m-rs1.dtsi from arch=arm") and use > > > a symlink. Note that in this case we put the files in a new > > > "include/common" directory since these snippets may need to be > > > referenced by dts files in many different subdirectories. > > > > I'd rather have something like this: > > > > https://marc.info/?m=147547436324674&w=2 > > > > Instead of having everybody move things over. I.e. make it easy to > > refer to the arm version from arm64 instead of creating a "common" > > layer inbetween. > > just so it gets noticed, I've done and tested [0], which hopefully should > implement your suggestions above. > > If that looks ok, how do you want that picked up? Should I just include > them in my regular rockchip branches or do you to pick them into some > immutable branch, if other surprise-users turn up in time for 4.12? Ping? I suppose we can prevent users in 4.12 by never merging this :) Brian > > > [0] http://lists.infradead.org/pipermail/linux-rockchip/2017-February/014226.html > > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html