lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 27 Feb 2017 19:20:48 +0100 From: Heiko Stuebner <heiko@...ech.de> To: Olof Johansson <olof@...om.net> Cc: Brian Norris <briannorris@...omium.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Doug Anderson <dianders@...omium.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>, Rob Herring <robh+dt@...nel.org>, Chris Zhong <zyw@...k-chips.com>, Stephen Barber <smbarber@...omium.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Caesar Wang <wxt@...k-chips.com> Subject: Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs Hi Olof, Am Dienstag, 21. Februar 2017, 15:47:31 CET schrieb Olof Johansson: > On Thu, Feb 9, 2017 at 5:05 PM, Brian Norris <briannorris@...omium.org> wrote: > > From: Douglas Anderson <dianders@...omium.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? Thanks Heiko [0] http://lists.infradead.org/pipermail/linux-rockchip/2017-February/014226.html
Powered by blists - more mailing lists