linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>,
	Erik Gilling <konkers@android.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Rob Clark <robclark@gmail.com>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
	lkml <linux-kernel@vger.kernel.org>,
	Android Kernel Team <kernel-team@android.com>
Subject: Re: [RFD] Proposal for merging Android sync driver in staging
Date: Wed, 27 Feb 2013 18:32:07 -0800	[thread overview]
Message-ID: <20130228023207.GB4042@kroah.com> (raw)
In-Reply-To: <512EBD80.8070101@linaro.org>

On Wed, Feb 27, 2013 at 06:14:24PM -0800, John Stultz wrote:
> I'd like to get a discussion going about submitting the Android sync
> driver to staging.
> 
> I know there is currently some very similar work going on with the
> dmabuf-fences, and rather then both approaches being worked out
> individually on their own, I suspect there could be better
> collaboration around this effort.
> 
> So my proposal is that we merge the Android sync driver into staging.
> 
> In my mind, this has the following benefits:
> 1) It allows other drivers that depend on the sync interface to also
> be submitted to staging, rather then forcing those drivers to be
> hidden away in various out of tree git repos, location unknown.
> 
> 2) It would provide a baseline view to the upstream community of the
> interface Android is using, providing  a real-world, active use case
> of the functionality.
> 
> Once the sync driver is in staging, if the dmabuf-fences work is
> fully sufficient to replace the Android sync driver, we should be
> able to whittle down the sync driver until its just a interface shim
> (and at which point efforts can be made to convert Android userland
> over to dmabuf-fences).

Sounds like a good plan to me.

> I've gone through the Android tree and reworked the sync driver to
> live in staging, while still preserving the full patch
> history/authorship. You can checkout the reworked patch queue here:
>  http://git.linaro.org/gitweb?p=people/jstultz/android-dev.git;a=shortlog;h=refs/heads/dev/sync-staging

I can't really look at a git tree at the moment, but will always be glad
to review patches.  Feel free to send them on and we can look at them
then :)

thanks,

greg k-h

  reply	other threads:[~2013-02-28  2:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28  2:14 [RFD] Proposal for merging Android sync driver in staging John Stultz
2013-02-28  2:32 ` Greg KH [this message]
2013-02-28 18:28   ` John Stultz
2013-02-28  3:03 ` Erik Gilling

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=20130228023207.GB4042@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=konkers@android.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@canonical.com \
    --cc=robclark@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).