All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: "Stéphane Marchesin" <marcheu@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/panel: update innolux n116bge timings
Date: Mon, 22 Sep 2014 10:35:18 +0200	[thread overview]
Message-ID: <20140922083517.GF1470@ulmo> (raw)
In-Reply-To: <CAGS+omDXZ6TONNuUaLkCGwMzuZ12OGQ0Ju8Jvsij4LW+drp2Lw@mail.gmail.com>


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

On Sun, Sep 21, 2014 at 03:53:51PM +0800, Daniel Kurtz wrote:
> Hi Thierry,
> 
> Congratulations!  I saw in one thread that you said you are out on
> paternity leave.

Thanks.

> You mentioned that you would be back around v3.17-rc6, which should be
> soonish, so just a gentle ping on this patch for when you return.

I'm back to work starting today but catching up on a lot of email, so
it might take me a little to get to the bottom of this.

Thierry

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

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

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

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	"David Airlie" <airlied@linux.ie>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Stéphane Marchesin" <marcheu@chromium.org>
Subject: Re: [PATCH] drm/panel: update innolux n116bge timings
Date: Mon, 22 Sep 2014 10:35:18 +0200	[thread overview]
Message-ID: <20140922083517.GF1470@ulmo> (raw)
In-Reply-To: <CAGS+omDXZ6TONNuUaLkCGwMzuZ12OGQ0Ju8Jvsij4LW+drp2Lw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

On Sun, Sep 21, 2014 at 03:53:51PM +0800, Daniel Kurtz wrote:
> Hi Thierry,
> 
> Congratulations!  I saw in one thread that you said you are out on
> paternity leave.

Thanks.

> You mentioned that you would be back around v3.17-rc6, which should be
> soonish, so just a gentle ping on this patch for when you return.

I'm back to work starting today but catching up on a lot of email, so
it might take me a little to get to the bottom of this.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-22  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  2:56 [PATCH] drm/panel: update innolux n116bge timings Daniel Kurtz
2014-09-02  2:56 ` Daniel Kurtz
2014-09-21  7:53 ` Daniel Kurtz
2014-09-21  7:53   ` Daniel Kurtz
2014-09-22  8:35   ` Thierry Reding [this message]
2014-09-22  8:35     ` Thierry Reding
2014-09-22  8:39 ` Thierry Reding
2014-09-22  8:39   ` Thierry Reding
2014-09-22 10:12   ` Daniel Kurtz
2014-09-22 10:12     ` Daniel Kurtz
2014-09-22 10:43     ` Thierry Reding
2014-09-22 10:43       ` Thierry Reding
2014-11-07 12:13     ` Thierry Reding
2014-11-07 12:13       ` Thierry Reding

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=20140922083517.GF1470@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=djkurtz@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcheu@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 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.