From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Gustavo Padovan <gustavo@padovan.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
"Daniel Stone" <daniels@collabora.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Riley Andrews" <riandrews@android.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Arve Hjønnevåg" <arve@android.com>,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"John Harrison" <John.C.Harrison@Intel.com>
Subject: Re: [PATCH 00/11] sync framework de-staging: part 1 - clean up
Date: Mon, 25 Jan 2016 12:23:52 +0100 [thread overview]
Message-ID: <56A605C8.8020703@linux.intel.com> (raw)
In-Reply-To: <1453380564-3328-1-git-send-email-gustavo@padovan.org>
Hey,
Op 21-01-16 om 13:49 schreef Gustavo Padovan:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Hi,
>
> The following patches are some clean ups on the sync framework before
> we start the actual de-staging. The main changes here are the move of
> SW_SYNC_USER to debugfs. Removal of struct sync_pt in favor of direct
> use of struct fence. And the rename of sync_fence to sync_file, a name
> to better reflect what it is for, a struct that connects struct fence(s)
> to a file.
>
> Please review. Thanks.
>
> Gustavo Padovan (11):
> staging/android: fix sync framework documentation
> staging/android: sync: remove interfaces that are not used
> staging/android: remove not used sync_timeline ops
> staging/android: create a 'sync' dir for debugfs information
> staging/android: move SW_SYNC_USER to a debugfs file
> staging/android: rename sync_fence to sync_file
> staging/android: rename 'sync_pt' to 'fence' in struct sync_fence_cb
> staging/android: remove struct sync_pt
> staging/android: remove unused var from sync_timeline_signal()
> staging/android: remove pointless sync_timeline_signal at destroy
> phase
> staging/android: remove sync_fence_create_dma()
>
For whole series:
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Renaming sync_fence to sync_file makes sense, it should hopefully reduce confusion.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-25 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 12:49 [PATCH 00/11] sync framework de-staging: part 1 - clean up Gustavo Padovan
2016-01-21 12:49 ` [PATCH 01/11] staging/android: fix sync framework documentation Gustavo Padovan
2016-01-21 12:49 ` [PATCH 02/11] staging/android: sync: remove interfaces that are not used Gustavo Padovan
2016-01-21 12:49 ` [PATCH 03/11] staging/android: remove not used sync_timeline ops Gustavo Padovan
2016-01-21 12:49 ` [PATCH 04/11] staging/android: create a 'sync' dir for debugfs information Gustavo Padovan
2016-01-21 12:49 ` [PATCH 05/11] staging/android: move SW_SYNC_USER to a debugfs file Gustavo Padovan
2016-01-21 12:49 ` [PATCH 06/11] staging/android: rename sync_fence to sync_file Gustavo Padovan
2016-01-21 12:49 ` [PATCH 07/11] staging/android: rename 'sync_pt' to 'fence' in struct sync_fence_cb Gustavo Padovan
2016-01-21 12:49 ` [PATCH 08/11] staging/android: remove struct sync_pt Gustavo Padovan
2016-01-21 12:49 ` [PATCH 09/11] staging/android: remove unused var from sync_timeline_signal() Gustavo Padovan
2016-01-21 12:49 ` [PATCH 10/11] staging/android: remove pointless sync_timeline_signal at destroy phase Gustavo Padovan
2016-01-21 12:49 ` [PATCH 11/11] staging/android: remove sync_fence_create_dma() Gustavo Padovan
2016-01-25 11:23 ` Maarten Lankhorst [this message]
2016-01-29 14:47 ` [PATCH 00/11] sync framework de-staging: part 1 - clean up Gustavo Padovan
2016-01-29 16:10 ` Greg Kroah-Hartman
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=56A605C8.8020703@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=John.C.Harrison@Intel.com \
--cc=arve@android.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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;
as well as URLs for NNTP newsgroup(s).