From: Matthias Kaehlcke <mka@chromium.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Harigovindan P <harigovi@codeaurora.org>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
sean@poorly.run, seanpaul@chromium.org
Subject: Re: [PATCH v10 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel
Date: Sun, 29 Mar 2020 10:44:17 -0700 [thread overview]
Message-ID: <20200329174417.GB199755@google.com> (raw)
In-Reply-To: <20200328204047.GG32230@ravnborg.org>
Hi Sam,
On Sat, Mar 28, 2020 at 09:40:47PM +0100, Sam Ravnborg wrote:
> Hi Harigovindan
>
> On Fri, Mar 27, 2020 at 01:06:34PM +0530, Harigovindan P wrote:
> > Adding support for visionox rm69299 panel driver and adding bindings for the same panel.
> >
> > Harigovindan P (2):
> > dt-bindings: display: add visionox rm69299 panel variant
> > drm/panel: add support for rm69299 visionox panel driver
>
> I have only the first patch, which is now applied.
> Please resend second patch as it is lost somewhere.
Yes, it seems for v8, v9 and v10 only the bindings were sent, even
though the cover letter and subject say it's a series of two patches.
To my knowledge the latest version of the driver patch is this:
https://patchwork.kernel.org/patch/11439689/
next prev parent reply other threads:[~2020-03-29 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:36 [PATCH v10 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P
2020-03-27 7:36 ` [PATCH v10 1/2] dt-bindings: display: add visionox rm69299 panel variant Harigovindan P
2020-03-28 20:40 ` Sam Ravnborg
2020-03-28 20:40 ` [PATCH v10 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Sam Ravnborg
2020-03-29 17:44 ` Matthias Kaehlcke [this message]
2020-03-30 19:25 ` Sam Ravnborg
2020-03-31 16:39 ` Matthias Kaehlcke
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=20200329174417.GB199755@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=sam@ravnborg.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).