From: Linus Walleij <linus.walleij@linaro.org>
To: Brian Masney <masneyb@onstation.org>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
MSM <linux-arm-msm@vger.kernel.org>,
freedreno@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 5/6] ARM: dts: qcom: msm8974-hammerhead: add support for backlight
Date: Mon, 6 May 2019 09:08:40 +0200 [thread overview]
Message-ID: <CACRpkdZ608b7+mh8Ln9N7EdGQmu2YNdZqRzoYjwfZXtcWqFE5g@mail.gmail.com> (raw)
In-Reply-To: <20190505130413.32253-6-masneyb@onstation.org>
On Sun, May 5, 2019 at 3:04 PM Brian Masney <masneyb@onstation.org> wrote:
> Add necessary device tree nodes for the main LCD backlight.
>
> Signed-off-by: Brian Masney <masneyb@onstation.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> This requires this series that I submitted to the LED / backlight
> subsystem:
> https://lore.kernel.org/lkml/20190424092505.6578-1-masneyb@onstation.org/
> It's received 3 {Reviewed,Acked}-Bys, and has no outstanding change
> requests, so I expect it'll be merged soon.
If the DT bindings are ACKed and reviewed we can merge DTS
files using it IMO.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-05-06 7:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 13:04 [PATCH RFC 0/6] ARM: qcom: initial Nexus 5 display support Brian Masney
2019-05-05 13:04 ` [PATCH RFC 1/6] drm/msm: fix null pointer dereference in msm_atomic_prepare_fb() Brian Masney
2019-05-05 13:04 ` [PATCH RFC 2/6] drm/msm: add dirty framebuffer helper Brian Masney
2019-05-05 13:04 ` [PATCH RFC 3/6] ARM: qcom_defconfig: add display-related options Brian Masney
2019-05-06 7:04 ` Linus Walleij
2019-05-05 13:04 ` [PATCH RFC 4/6] ARM: dts: msm8974: add display support Brian Masney
2019-05-06 7:07 ` Linus Walleij
2019-05-07 6:39 ` Bjorn Andersson
2019-05-09 2:16 ` Brian Masney
2019-05-09 2:25 ` Rob Clark
[not found] ` <CAF6AEGsM382jB=h7oM3frhZ5fAp+qYUdgiiKSKo1RtR8+ffjrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-09 3:00 ` Bjorn Andersson
2019-05-09 7:12 ` Brian Masney
2019-05-09 14:38 ` Rob Clark
2019-05-09 14:59 ` Bjorn Andersson
2019-05-05 13:04 ` [PATCH RFC 5/6] ARM: dts: qcom: msm8974-hammerhead: add support for backlight Brian Masney
2019-05-06 7:08 ` Linus Walleij [this message]
2019-05-05 13:04 ` [PATCH RFC 6/6] ARM: dts: qcom: msm8974-hammerhead: add support for display Brian Masney
2019-05-06 7:09 ` Linus Walleij
2019-05-06 6:42 ` [PATCH RFC 0/6] ARM: qcom: initial Nexus 5 display support Linus Walleij
[not found] ` <CACRpkda=JTfKC4z=1Gmt1BE5adwd8XGZ4ERTgapWX_BN9TFESw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-06 8:46 ` Brian Masney
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=CACRpkdZ608b7+mh8Ln9N7EdGQmu2YNdZqRzoYjwfZXtcWqFE5g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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).