All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Pending panel driver patches - OK to commit?
Date: Wed, 3 Apr 2019 18:50:12 +0200	[thread overview]
Message-ID: <20190403165012.GA3184@ulmo> (raw)
In-Reply-To: <CAMty3ZCm6AzASoJo9X3AOa9m0FUqycmDy83Fu6cMYOgWN4Gk+w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]

On Wed, Apr 03, 2019 at 10:15:50PM +0530, Jagan Teki wrote:
> Hi Sam,
> 
> On Mon, Apr 1, 2019 at 11:54 PM Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > Hi Thierry.
> >
> > We have a few panel drivers that are reviewed, at least by me,
> > and next step is either to have someone else to step up and
> > do review or to have them applied to drm-misc.
> >
> > Rocktech jh057n00900 - from Guido Günther <agx@sigxcpu.org>
> > - final version posted just now
> >
> > Novatek NT35596 - from Jagan Teki <jagan@amarulasolutions.com>
> > - final version posted some time ago
> 
> About this panel, I need to send next version for fixing few comments
> from your side. There is another one which will be in ML since from
> weeks, here [1]
> 
> [1] https://patchwork.freedesktop.org/patch/285704/

I applied this earlier and it should be hitting linux-next tomorrow.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-04-03 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 18:24 Pending panel driver patches - OK to commit? Sam Ravnborg
2019-04-03 16:37 ` Thierry Reding
2019-04-03 16:45 ` Jagan Teki
2019-04-03 16:50   ` Thierry Reding [this message]
2019-04-22 18:18 ` Fabio Estevam

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=20190403165012.GA3184@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.