All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Jan Vesely <jan.vesely@rutgers.edu>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm 1/1] drmsltest: Check expected neighbours
Date: Mon, 21 Aug 2017 13:19:36 +0100	[thread overview]
Message-ID: <CACvgo50s1DZD+raFieQWKnxm0QDJk3SJGtnZPYq2y2DhxL7sBg@mail.gmail.com> (raw)
In-Reply-To: <CACvgo50+GX3Z4mhKpjD0K84HZmJTY2VYV53KDOGwHZt=vtuM_A@mail.gmail.com>

On 16 August 2017 at 02:51, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> Hi Jan,
>
> On 14 August 2017 at 03:44, Jan Vesely <jan.vesely@rutgers.edu> wrote:
>> On Fri, 2017-07-28 at 10:23 -0400, Jan Vesely wrote:
>>> Fixes: 7d8c9464081634f053e16e5eac9655a12fae1dc4
>>> Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
>>
>> ping.
>> Emil, should I just drop this patch?
>> another alternative is to remove the list implementation entirely,
>> since nobody noticed when it got broken.
>>
> libdrm stuff has been under my radar for a bit.
> I'll try to take a look tomorrow/the day after.
>
> I've been travelling over the last few days and I'm still in the
> middle of it :-\
>
Thanks for the patience Jan.
Pushed the patch to master.

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

  reply	other threads:[~2017-08-21 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 14:23 [PATCH libdrm 1/1] drmsltest: Check expected neighbours Jan Vesely
2017-08-14  2:44 ` Jan Vesely
2017-08-16  1:51   ` Emil Velikov
2017-08-21 12:19     ` Emil Velikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-26 17:15 Jan Vesely

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=CACvgo50s1DZD+raFieQWKnxm0QDJk3SJGtnZPYq2y2DhxL7sBg@mail.gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jan.vesely@rutgers.edu \
    /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.