From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
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>,
pavel@ucw.cz, "Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"John Harrison" <John.C.Harrison@Intel.com>
Subject: Re: [PATCH v2 0/6] de-stage SW_SYNC validation frawework
Date: Thu, 11 Aug 2016 10:24:35 +0100 [thread overview]
Message-ID: <20160811092435.GN10429@imgtec.com> (raw)
In-Reply-To: <1470691462-19140-1-git-send-email-gustavo@padovan.org>
On Mon, Aug 08, 2016 at 06:24:16PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> Hi Greg,
>
> This is the last step in the Sync Framwork de-stage task. It de-stage
> the SW_SYNC validation framework and the sync_debug info debugfs file.
>
> The first 2 patches are clean up and improvements and the rest is preparation
> to de-stage and then finally the actual de-stage.
>
> v2:
> - add documentation about the SW_SYNC ioctl API (comments from Pavel Machek)
> - remove for now patch to add sync_pt name to debugfs
>
> Please review,
>
> Gustavo
>
> ---
> Gustavo Padovan (6):
> staging/android: remove doc from sw_sync
> staging/android: do not let userspace trigger WARN_ON
> staging/android: move trace/sync.h to sync_trace.h
> staging/android: prepare sw_sync files for de-staging
> staging/android: add Doc for SW_SYNC ioctl interface
> dma-buf/sw_sync: de-stage SW_SYNC
>
> drivers/dma-buf/Kconfig | 13 ++
> drivers/dma-buf/Makefile | 1 +
> drivers/dma-buf/sw_sync.c | 349 +++++++++++++++++++++++++++++++++++
> drivers/dma-buf/sync_debug.c | 230 +++++++++++++++++++++++
> drivers/dma-buf/sync_debug.h | 69 +++++++
> drivers/dma-buf/sync_trace.h | 32 ++++
> drivers/staging/android/Kconfig | 13 --
> drivers/staging/android/Makefile | 1 -
> drivers/staging/android/sw_sync.c | 344 ----------------------------------
> drivers/staging/android/sync_debug.c | 230 -----------------------
> drivers/staging/android/sync_debug.h | 84 ---------
> drivers/staging/android/trace/sync.h | 32 ----
> 12 files changed, 694 insertions(+), 704 deletions(-)
> create mode 100644 drivers/dma-buf/sw_sync.c
> create mode 100644 drivers/dma-buf/sync_debug.c
> create mode 100644 drivers/dma-buf/sync_debug.h
> create mode 100644 drivers/dma-buf/sync_trace.h
> delete mode 100644 drivers/staging/android/sw_sync.c
> delete mode 100644 drivers/staging/android/sync_debug.c
> delete mode 100644 drivers/staging/android/sync_debug.h
> delete mode 100644 drivers/staging/android/trace/sync.h
When you send your next revision, could you use `git format-patch -M`?
A good 95% of the lines in these patches aren't actually modified, just
moved around, which makes it much harder to spot the actual changes :)
Cheers,
Eric
>
> --
> 2.5.5
next prev parent reply other threads:[~2016-08-11 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 21:24 [PATCH v2 0/6] de-stage SW_SYNC validation frawework Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 1/6] staging/android: remove doc from sw_sync Gustavo Padovan
2016-08-08 23:41 ` Pavel Machek
2016-08-11 15:06 ` Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 2/6] staging/android: do not let userspace trigger WARN_ON Gustavo Padovan
2016-08-08 21:24 ` [PATCH v2 3/6] staging/android: move trace/sync.h to sync_trace.h Gustavo Padovan
2016-08-11 9:41 ` Eric Engestrom
2016-08-08 21:24 ` [PATCH v2 4/6] staging/android: prepare sw_sync files for de-staging Gustavo Padovan
2016-08-11 9:42 ` Eric Engestrom
2016-08-08 21:24 ` [PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface Gustavo Padovan
2016-08-11 9:43 ` Eric Engestrom
2016-08-08 21:24 ` [PATCH v2 6/6] dma-buf/sw_sync: de-stage SW_SYNC Gustavo Padovan
2016-08-11 9:56 ` Eric Engestrom
2016-08-11 9:24 ` Eric Engestrom [this message]
2016-08-11 15:09 ` [PATCH v2 0/6] de-stage SW_SYNC validation frawework Gustavo Padovan
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=20160811092435.GN10429@imgtec.com \
--to=eric.engestrom@imgtec.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=pavel@ucw.cz \
--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