From: Matthias Kaehlcke <mka@chromium.org>
To: Harigovindan P <harigovi@codeaurora.org>
Cc: sean@poorly.run, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
seanpaul@chromium.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH v7 2/2] drm/panel: add support for rm69299 visionox panel driver
Date: Mon, 16 Mar 2020 10:00:20 -0700 [thread overview]
Message-ID: <20200316170020.GO144492@google.com> (raw)
In-Reply-To: <20200316041647.27953-3-harigovi@codeaurora.org>
On Mon, Mar 16, 2020 at 09:46:47AM +0530, Harigovindan P wrote:
> Add support for Visionox panel driver.
>
> Signed-off-by: Harigovindan P <harigovi@codeaurora.org>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-16 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 4:16 [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P
2020-03-16 4:16 ` [PATCH v7 1/2] dt-bindings: display: add visionox rm69299 panel variant Harigovindan P
2020-03-20 1:01 ` Rob Herring
2020-03-16 4:16 ` [PATCH v7 2/2] drm/panel: add support for rm69299 visionox panel driver Harigovindan P
2020-03-16 17:00 ` Matthias Kaehlcke [this message]
2020-03-20 5:44 ` Harigovindan P
2020-03-23 5:03 ` Harigovindan P
2020-03-27 7:36 ` Harigovindan P
2020-04-15 19:08 ` Matthias Kaehlcke
-- strict thread matches above, loose matches on Subject: below --
2020-03-16 4:12 [PATCH v7 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P
2020-03-16 4:13 ` [PATCH v7 2/2] drm/panel: add support for rm69299 visionox panel driver Harigovindan P
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=20200316170020.GO144492@google.com \
--to=mka@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=harigovi@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.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).