From: Gustavo Padovan <gustavo@padovan.org>
To: Sumit Semwal <sumit.semwal@linaro.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 mailing list" <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
"John Harrison" <John.C.Harrison@intel.com>
Subject: Re: [PATCH] dma-buf/sync_file: de-stage sync_file
Date: Wed, 23 Mar 2016 11:59:13 -0300 [thread overview]
Message-ID: <20160323145913.GA4121@joana> (raw)
In-Reply-To: <CAO_48GGProh0=5aQ_4dK=LxaMSJXLmO5KAjWr40BCMe5PNtUoQ@mail.gmail.com>
Hi Sumit,
2016-03-21 Sumit Semwal <sumit.semwal@linaro.org>:
> Thanks for the patch, Gustavo!
>
> On 18 March 2016 at 19:49, Gustavo Padovan <gustavo@padovan.org> wrote:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > sync_file is useful to connect one or more fences to the file. The file is
> > used by userspace to track fences.
> >
> I think it is worthwhile to add relevant bits to the Documentation as
> well - care to add relevant stuff to either Documentation/dma_buf.txt,
> or to a file of its own? (I'd prefer the former, but would leave it
> upto you.)
Sure, that is part of my plan. I'm currently trying to have a working
version of fences on DRM then I think I'll be able to add Documentation
for everything I have done.
Gustavo
prev parent reply other threads:[~2016-03-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 14:19 [PATCH] de-stage android sync framework Gustavo Padovan
2016-03-18 14:19 ` [PATCH] dma-buf/sync_file: de-stage sync_file Gustavo Padovan
2016-03-21 7:02 ` Sumit Semwal
2016-03-23 14:59 ` Gustavo Padovan [this message]
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=20160323145913.GA4121@joana \
--to=gustavo@padovan.org \
--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=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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