linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [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	[thread overview]
Message-ID: <20170320230748.GA97915@google.com> (raw)
In-Reply-To: <1529949.5djtX72aeJ@phil>

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
> 
> 

  reply	other threads:[~2017-03-20 23:07 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
2017-02-21 23:47   ` Olof Johansson
2017-02-27 18:20     ` Heiko Stuebner
2017-03-20 23:07       ` Brian Norris [this message]
2017-04-19 12:54       ` Olof Johansson
2017-04-19 13:25         ` Heiko Stuebner
2017-04-19 13:31           ` Olof Johansson
2017-02-10  1:05 ` [PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399 Brian Norris
2017-02-10 22:01   ` Heiko Stuebner
2017-02-10  1:05 ` [PATCH v2 3/6] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
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
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
2017-02-10  1:05 ` [PATCH v2 6/6] arm64: dts: rockchip: sort rk3399 by unit address Brian Norris
2017-02-10 21:39   ` Heiko Stuebner

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=20170320230748.GA97915@google.com \
    --to=briannorris@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).