From: Gustavo Padovan <gustavo@padovan.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Gustavo Padovan <gustavo.padovan@collabora.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] dma-buf/sw_sync: move timeline_fence_ops around
Date: Mon, 31 Jul 2017 16:32:34 -0300 [thread overview]
Message-ID: <20170731193234.GA1882@jade> (raw)
In-Reply-To: <150140574817.3218.5294461513222205273@mail.alporthouse.com>
2017-07-30 Chris Wilson <chris@chris-wilson.co.uk>:
> Quoting Gustavo Padovan (2017-07-29 16:22:15)
> > From: Gustavo Padovan <gustavo.padovan@collabora.com>
> >
> > We are going to use timeline_fence_signaled() in a internal function in
> > the next commit.
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com>
>
> Purely mechanical,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks for reviewing. Pushed to drm-misc-next.
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-07-31 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 15:22 [PATCH 1/3] dma-buf/sw_sync: move timeline_fence_ops around Gustavo Padovan
2017-07-29 15:22 ` [PATCH 2/3] dma-buf/sw_sync: clean up list before signaling the fence Gustavo Padovan
2017-07-30 9:10 ` Chris Wilson
2017-07-31 19:32 ` Gustavo Padovan
2017-07-29 15:22 ` [PATCH 3/3] selftests: sync: add test that closes the fd before fence signal Gustavo Padovan
2017-07-30 9:20 ` Chris Wilson
2017-07-31 19:43 ` Gustavo Padovan
2017-08-02 19:45 ` Shuah Khan
2017-08-02 20:28 ` Gustavo Padovan
2017-07-30 9:09 ` [PATCH 1/3] dma-buf/sw_sync: move timeline_fence_ops around Chris Wilson
2017-07-31 19:32 ` Gustavo Padovan [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=20170731193234.GA1882@jade \
--to=gustavo@padovan.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.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