From: Heiko Stuebner <heiko@sntech.de>
To: Olof Johansson <olof@lixom.net>
Cc: Brian Norris <briannorris@chromium.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Chris Zhong <zyw@rock-chips.com>,
Stephen Barber <smbarber@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Caesar Wang <wxt@rock-chips.com>
Subject: Re: [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs
Date: Mon, 27 Feb 2017 19:20:48 +0100 [thread overview]
Message-ID: <1529949.5djtX72aeJ@phil> (raw)
In-Reply-To: <CAOesGMiim2WFfEAg-bJmWTwWn69=V_GuEg6AxsxPYMyzd3KFUw@mail.gmail.com>
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@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?
Thanks
Heiko
[0] http://lists.infradead.org/pipermail/linux-rockchip/2017-February/014226.html
next prev parent reply other threads:[~2017-02-27 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 1:05 [PATCH v2 0/6] arm64: dts: rockchip: support Google Kevin Brian Norris
2017-02-10 1:05 ` [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs Brian Norris
[not found] ` <20170210010521.78872-2-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-21 23:47 ` Olof Johansson
2017-02-27 18:20 ` Heiko Stuebner [this message]
2017-03-20 23:07 ` Brian Norris
2017-04-19 12:54 ` Olof Johansson
[not found] ` <CAOesGMirj2j5P7_Ri4CSCux+O3hH_wxvrra7-p33AdXO4Ej5Hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-19 13:25 ` Heiko Stuebner
2017-04-19 13:31 ` Olof Johansson
[not found] ` <20170210010521.78872-1-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 1:05 ` [PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399 Brian Norris
[not found] ` <20170210010521.78872-3-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 22:01 ` Heiko Stuebner
2017-02-10 1:05 ` [PATCH v2 6/6] arm64: dts: rockchip: sort rk3399 by unit address Brian Norris
[not found] ` <20170210010521.78872-7-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 21:39 ` Heiko Stuebner
2017-02-10 1:05 ` [PATCH v2 3/6] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
[not found] ` <20170210010521.78872-4-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-16 2:12 ` Rob Herring
2017-02-10 1:05 ` [PATCH v2 4/6] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
[not found] ` <20170210010521.78872-5-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-28 22:00 ` Heiko Stuebner
2017-02-28 22:54 ` Doug Anderson
2017-02-10 1:05 ` [PATCH v2 5/6] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators Brian Norris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1529949.5djtX72aeJ@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=wxt@rock-chips.com \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).