public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>,
	"open list:GENERIC INCLUDE/A..." <linux-arch@vger.kernel.org>,
	Thomas Hellstrom <thellstrom@vmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	"Clark, Rob" <robdclark@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Colin Cross <ccross@google.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 0/9] Updated fence patch series
Date: Tue, 8 Jul 2014 10:52:17 -0700	[thread overview]
Message-ID: <20140708175217.GA11121@kroah.com> (raw)
In-Reply-To: <CAO_48GHwJ4EuCKgLmZhEaEQqS9e7EVZP3hsivhRwLCNFhzAQVA@mail.gmail.com>

On Tue, Jul 08, 2014 at 08:22:11PM +0530, Sumit Semwal wrote:
> On 8 July 2014 20:09, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Jul 08, 2014 at 03:44:27PM +0200, Daniel Vetter wrote:
> >> On Mon, Jul 07, 2014 at 10:30:52AM -0700, Greg KH wrote:
> >> > On Mon, Jul 07, 2014 at 03:23:17PM +0200, Daniel Vetter wrote:
> >> > > On Wed, Jul 2, 2014 at 7:37 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> > > >> Android can expose fences to userspace. It's possible to make the new fence
> >> > > >> mechanism expose the same fences to userspace by changing sync_fence_create
> >> > > >> to take a struct fence instead of a struct sync_pt. No other change is needed,
> >> > > >> because only the fence parts of struct sync_pt are used. But because the
> >> > > >> userspace fences are a separate problem and I haven't really looked at it yet
> >> > > >> I feel it should stay in staging, for now.
> >> > > >
> >> > > > Ok, that's reasonable.
> >> > > >
> >> > > > At first glance, this all looks "sane" to me, any objection from anyone
> >> > > > if I merge this through my driver-core tree for 3.17?
> >> > >
> >> > > Ack from my side fwiw.
> >> >
> >> > Thanks, I'll queue it up later today.
> >>
> >> btw should we add you as a (co)maintainer for driver/core/dma-buf since
> >> you seem to want to keep a closer tab on what the insane gfx folks are up
> >> to in there?
> >
> > Sure, why not, what's one more maintainership...
> >
> > Oh, does that mean you want me to be the one collecting the patches and
> > forwarding them on to Linus?  If so, that's fine, I can easily do that
> > as well due to my infrastructure being set up for it.
> >
> If you're ok, I could continue to do the collecting / forwarding
> business - I guess Daniel meant more from the 'not miss patches that
> need review'!

Hey, I'm more than willing to have other people do the real work of
collecting / forwarding :)

I'll just review stuff as it floats by, that's not enough of a role to
put me in "MAINTAINERS" at all.

thanks,

greg k-h

  reply	other threads:[~2014-07-08 17:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 10:57 [PATCH v2 0/9] Updated fence patch series Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 1/9] dma-buf: move to drivers/dma-buf Maarten Lankhorst
2014-07-01 11:06   ` Arend van Spriel
2014-07-01 11:09     ` Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 2/9] fence: dma-buf cross-device synchronization (v18) Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 3/9] seqno-fence: Hardware dma-buf implementation of fencing (v6) Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 4/9] dma-buf: use reservation objects Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 5/9] android: convert sync to fence api, v6 Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 6/9] reservation: add support for fences to enable cross-device synchronisation Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 7/9] dma-buf: add poll support, v3 Maarten Lankhorst
2014-07-01 10:57 ` [PATCH v2 8/9] reservation: update api and add some helpers Maarten Lankhorst
2014-07-01 10:58 ` [PATCH v2 9/9] reservation: add suppport for read-only access using rcu Maarten Lankhorst
2014-07-02  5:37 ` [PATCH v2 0/9] Updated fence patch series Greg KH
2014-07-02  9:12   ` Maarten Lankhorst
2014-07-08 20:46     ` Greg KH
2014-07-07 13:23   ` Daniel Vetter
2014-07-07 17:30     ` Greg KH
2014-07-08 13:44       ` Daniel Vetter
2014-07-08 14:39         ` Greg KH
2014-07-08 14:52           ` Sumit Semwal
2014-07-08 17:52             ` Greg KH [this message]
2014-07-07 17:27   ` Sumit Semwal

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=20140708175217.GA11121@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ccross@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@canonical.com \
    --cc=robdclark@gmail.com \
    --cc=sumit.semwal@linaro.org \
    --cc=thellstrom@vmware.com \
    --cc=thierry.reding@gmail.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