Re: [PATCH] staging/android: add TODO to de-stage android sync framework

[Daniel Vetter]

On Mon, Nov 23, 2015 at 05:41:53PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@xxxxxxxxxxxxxxx>
> 
>  - remove sw_sync, it is used only for testing/debugging and should not
> be upstreamed.
>  - port sw_sync testcases to use debugfs somehow
>  - clean up and ABI check for security issues
>  - move the sync framework to drivers/base/dma-buf
> 
> Cc: Arve Hjønnevåg <arve@xxxxxxxxxxx>
> Cc: Riley Andrews <riandrews@xxxxxxxxxxx>
> Cc: Daniel Vetter <daniel.vetter@xxxxxxxx>
> Cc: Rob Clark <robdclark@xxxxxxxxx>
> Cc: Greg Hackmann <ghackmann@xxxxxxxxxx>
> Cc: John Harrison <John.C.Harrison@xxxxxxxxx>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@xxxxxxxxxxxxxxx>

This reflects my recollection of various discussions at conferences and on
irc. Acked-by: Daniel Vetter <daniel.vetter@xxxxxxxx>

> ---
>  drivers/staging/android/TODO | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/staging/android/TODO b/drivers/staging/android/TODO
> index 8f3ac37..2375dae 100644
> --- a/drivers/staging/android/TODO
> +++ b/drivers/staging/android/TODO
> @@ -25,5 +25,12 @@ ion/
>     exposes existing cma regions and doesn't reserve unecessarily memory when
>     booting a system which doesn't use ion.
>  
> +sync framework:
> + - remove sw_sync, it is used only for testing/debugging and should not be
> +upstreamed.
> + - port sw_sync testcases to use debugfs somehow
> + - clean up and ABI check for security issues
> + - move it to drivers/base/dma-buf
> +
>  Please send patches to Greg Kroah-Hartman <greg@xxxxxxxxx> and Cc:
>  Arve Hjønnevåg <arve@xxxxxxxxxxx> and Riley Andrews <riandrews@xxxxxxxxxxx>
> -- 
> 2.1.0
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/