public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Enric Balletbo Serra
	<eballetbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] arm64: dts: rockchip: move backlight from sapphire to excavator
Date: Fri, 02 Nov 2018 13:12:53 +0100	[thread overview]
Message-ID: <5566033.xjZbm30eH9@phil> (raw)
In-Reply-To: <20181030150049.16064-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Am Dienstag, 30. Oktober 2018, 16:00:49 CET schrieb Vicente Bergas:
> The backlight is for the eDP panel and it has the connector on the excavator baseboard.
> 
> Signed-off-by: Vicente Bergas <vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

applied for 4.21 (or whatever it will be called)

The patch itself is good, as it as Vicene said only moved the elements
and the resulting dtb stays identical for excavator.

Enric, you can propose a patch on top, that removes the backlight
elements. That way if someone really finds an issue with it, we
have a clean revert path, which still keeps Vicente's move intact.


Heiko

  parent reply	other threads:[~2018-11-02 12:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 15:00 [PATCH] arm64: dts: rockchip: move backlight from sapphire to excavator Vicente Bergas
     [not found] ` <20181030150049.16064-1-vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-30 16:58   ` Enric Balletbo Serra
     [not found]     ` <CAFqH_51Bk4RhS5+866XUL_qXTnofg92yT6Yig9gNVytAt+H=bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-30 17:19       ` Vicente Bergas
2018-11-02 12:12   ` Heiko Stuebner [this message]
2018-11-02 12:20     ` Vicente Bergas
     [not found]       ` <CAAMcf8CuHWWEUF=C4B=ZdyjR=gv5M2N+GBRQ1DjXUs7L704yRg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-11-02 12:22         ` 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=5566033.xjZbm30eH9@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=eballetbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=vicencb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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