Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1605195 > unrolled thread

Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs

Started byBrian Norris <briannorris@chromium.org>
First post2017-03-21 00:10 +0100
Last post2017-03-21 00:10 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and  cros-ec-sbs Brian Norris <briannorris@chromium.org> - 2017-03-21 00:10 +0100

#1605195 — Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs

FromBrian Norris <briannorris@chromium.org>
Date2017-03-21 00:10 +0100
SubjectRe: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs
Message-ID<tneB4-3ga-23@gated-at.bofh.it>
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 <briannorris@chromium.org> wrote:
> > > From: Douglas Anderson <dianders@chromium.org>
> > > 
> > > 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
> 
> 

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web