dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: Hyungwon Hwang <human.hwang@samsung.com>
Cc: Emil Velikov <emil.l.velikov@gmail.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v3 1/3] modetest: introduce get_prop_info() for getting property id and type
Date: Mon, 7 Dec 2015 17:37:13 +0100	[thread overview]
Message-ID: <20151207163712.GB4450@ulmo.nvidia.com> (raw)
In-Reply-To: <20151127113733.5aeb314f@hwh-ubuntu>


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

On Fri, Nov 27, 2015 at 11:37:33AM +0900, Hyungwon Hwang wrote:
> Hello all,
> 
> +To Thierry Reding
> 
> On Thu, 26 Nov 2015 16:42:01 +0000
> Emil Velikov <emil.l.velikov@gmail.com> wrote:
> 
> > Hi Hyungwon
> > 
> > I completely missed out that you've sent an updated version of the
> > series. I will take a look at them later on tonight. Meanwhile have
> > you looked at the atomic tests/helpers work from Thierry [1] ? It
> > creates nice simple helpers (as opposed to a single massive C file
> > like modetest) and I'm leaning that there is quite a lot of code that
> > can be reused from there.
> > 
> > Speaking of which Thierry,
> > What is happening with these patches ? Last time you've respun them
> > I've pinged you to send them over for inclusion. There was a trivial
> > fix needed here or there but they were in pretty good shape.
> 
> Yes. I checked it now. It would be more clear concise, if they comes.
> Would it be better to wait Thierry for sending them again? Can you
> afford to do that, Thierry?

Yeah, I think I can do that. It'll probably take until tomorrow for me
to find a free slot to rebase and send out again.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- 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

      reply	other threads:[~2015-12-07 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  2:45 [PATCH v3 1/3] modetest: introduce get_prop_info() for getting property id and type Hyungwon Hwang
2015-09-23  2:45 ` [PATCH v3 2/3] modetest: add atomic modeset support Hyungwon Hwang
2015-11-26 23:42   ` Emil Velikov
2015-09-23  2:45 ` [PATCH v3 3/3] modetest: add atomic page flip support Hyungwon Hwang
2015-11-26 23:57   ` Emil Velikov
2015-11-26 16:42 ` [PATCH v3 1/3] modetest: introduce get_prop_info() for getting property id and type Emil Velikov
2015-11-27  2:37   ` Hyungwon Hwang
2015-12-07 16:37     ` Thierry Reding [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=20151207163712.GB4450@ulmo.nvidia.com \
    --to=treding@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=human.hwang@samsung.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