From: Pavel Machek <pavel@ucw.cz>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
dri-devel@lists.freedesktop.org,
"Daniel Stone" <daniels@collabora.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Rob Clark" <robdclark@gmail.com>,
"Greg Hackmann" <ghackmann@google.com>,
"John Harrison" <John.C.Harrison@Intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 0/7] de-stage SW_SYNC validation frawework
Date: Sun, 26 Jun 2016 23:45:04 +0200 [thread overview]
Message-ID: <20160626214504.GA21026@amd> (raw)
In-Reply-To: <1466437993-21573-1-git-send-email-gustavo@padovan.org>
Hi!
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Hi Greg,
>
> This is the last step in the Sync Framwork de-stage task. It
Typo: "fram_e_work"
> de-stage
> the SW_SYNC validation framework and the sync_debug info debugfs file.
>
> The first 3 patches are clean up and improvements and the rest is preparation
> to de-stage and then finally the actual de-stage.
Could we get some kind of description what the sync framework does?
There are no useful comments in /sw_sync.c. There's no Documentation/
files. I don't know what this is supposed to do...
Pavel
> Please review,
>
> Gustavo
>
> ---
> Gustavo Padovan (7):
> staging/android: move trace/sync.h to sync_trace.h
> staging/android: remove doc from sw_sync
> staging/android: display sync_pt name on debugfs
> staging/android: do not let userspace trigger WARN_ON
> staging/android: prepare sw_sync files for de-staging
> dma-buf/sw_sync: de-stage SW_SYNC
> staging/android: remove sync framework TODO
>
> drivers/dma-buf/Kconfig | 14 +++++++
> drivers/dma-buf/Makefile | 1 +
> drivers/{staging/android => dma-buf}/sw_sync.c | 46 +++-------------------
> drivers/{staging/android => dma-buf}/sync_debug.c | 7 ++--
> drivers/{staging/android => dma-buf}/sync_debug.h | 26 +++++-------
> .../android/trace/sync.h => dma-buf/sync_trace.h} | 6 +--
> drivers/staging/android/Kconfig | 13 ------
> drivers/staging/android/Makefile | 1 -
> drivers/staging/android/TODO | 8 ----
> 9 files changed, 38 insertions(+), 84 deletions(-)
> rename drivers/{staging/android => dma-buf}/sw_sync.c (84%)
> rename drivers/{staging/android => dma-buf}/sync_debug.c (97%)
> rename drivers/{staging/android => dma-buf}/sync_debug.h (72%)
> rename drivers/{staging/android/trace/sync.h => dma-buf/sync_trace.h} (84%)
>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-06-26 21:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 15:53 [PATCH 0/7] de-stage SW_SYNC validation frawework Gustavo Padovan
2016-06-20 15:53 ` [PATCH 1/7] staging/android: remove doc from sw_sync Gustavo Padovan
2016-06-20 15:53 ` [PATCH 2/7] staging/android: display sync_pt name on debugfs Gustavo Padovan
2016-08-08 9:34 ` Maarten Lankhorst
2016-08-08 19:59 ` Gustavo Padovan
2016-08-09 10:04 ` Maarten Lankhorst
2016-08-09 14:45 ` Gustavo Padovan
2016-06-20 15:53 ` [PATCH 3/7] staging/android: do not let userspace trigger WARN_ON Gustavo Padovan
2016-06-20 15:53 ` [PATCH 4/7] staging/android: move trace/sync.h to sync_trace.h Gustavo Padovan
2016-06-20 15:53 ` [PATCH 5/7] staging/android: prepare sw_sync files for de-staging Gustavo Padovan
2016-06-20 16:09 ` Joe Perches
2016-06-20 16:16 ` Gustavo Padovan
2016-06-22 20:33 ` [PATCH v2] " Gustavo Padovan
2016-06-20 15:53 ` [PATCH 6/7] dma-buf/sw_sync: de-stage SW_SYNC Gustavo Padovan
2016-06-20 15:53 ` [PATCH 7/7] staging/android: remove sync framework TODO Gustavo Padovan
2016-06-22 23:46 ` Emil Velikov
2016-06-23 13:33 ` Gustavo Padovan
2016-06-26 21:45 ` Pavel Machek [this message]
2016-07-07 19:39 ` [PATCH 0/7] de-stage SW_SYNC validation frawework Gustavo Padovan
2016-07-18 19:12 ` Gustavo Padovan
2016-07-24 22:21 ` Greg Kroah-Hartman
2016-08-07 21:51 ` Pavel Machek
2016-08-08 19:08 ` Gustavo Padovan
2016-07-24 15:00 ` Pavel Machek
2016-08-08 19:53 ` Gustavo Padovan
2016-08-09 6:04 ` Daniel Vetter
2016-08-10 20:53 ` Pavel Machek
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=20160626214504.GA21026@amd \
--to=pavel@ucw.cz \
--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=ghackmann@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=riandrews@android.com \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.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 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).