dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Marek Vasut <marex@denx.de>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH V2] drm/panel: simple: Fix bus flags for ortustech com43h4m85ulc
Date: Fri, 16 Sep 2016 17:37:10 +0200	[thread overview]
Message-ID: <1474040230.2491.84.camel@pengutronix.de> (raw)
In-Reply-To: <20160916151727.GB12753@ulmo.ba.sec>

Hi Thierry,

Am Freitag, den 16.09.2016, 17:17 +0200 schrieb Thierry Reding:
> On Fri, Aug 26, 2016 at 06:26:00PM +0200, Marek Vasut wrote:
> > This display expects DE pin and data lines to be active high,
> > add the necessary flags.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Philipp Zabel <p.zabel@pengutronix.de>
> > Cc: Thierry Reding <treding@nvidia.com>
> > ---
> > V2: Add DRM_BUS_FLAG_PIXDATA_POSEDGE to cater for the video data.
> > ---
> >  drivers/gpu/drm/panel/panel-simple.c | 1 +
> >  1 file changed, 1 insertion(+)
> 
> Applied, thanks. I did add Philipp's Reviewed-by from v1, which I assume
> would stand since he had suggested the PIXDATA_POSEDGE. I've Cc'ed him
> now (it seems your v2 post didn't include him) so he can speak up if he
> wants me to remove the Reviewed-by again.
> 
> Thierry

I received v2, just didn't think to re-assert the Reviewed-by. Thank you
for bringing it to my attention, I agree with your deduction.

regards
Philipp

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

      reply	other threads:[~2016-09-16 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 16:26 [PATCH V2] drm/panel: simple: Fix bus flags for ortustech com43h4m85ulc Marek Vasut
2016-09-16 15:17 ` Thierry Reding
2016-09-16 15:37   ` Philipp Zabel [this message]

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=1474040230.2491.84.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=marex@denx.de \
    --cc=thierry.reding@gmail.com \
    /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