From: Tiago Vignatti <tiago.vignatti@intel.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Daniel Vetter" <daniel.vetter@intel.com>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
devel@driverdev.osuosl.org, "Hans Verkuil" <hverkuil@xs4all.nl>
Subject: Re: [PATCH] dma-buf: Update docs for SYNC ioctl
Date: Tue, 29 Mar 2016 14:20:20 -0300 [thread overview]
Message-ID: <56FAB954.2060408@intel.com> (raw)
In-Reply-To: <CANq1E4Q-aXTx5YGh0yOiU8cRh_opqrUrGin7qn-9N_EszjXfvA@mail.gmail.com>
On 03/29/2016 06:47 AM, David Herrmann wrote:
> Hi
>
> On Mon, Mar 28, 2016 at 9:42 PM, Tiago Vignatti
> <tiago.vignatti@intel.com> wrote:
>> Do we have an agreement here after all? David? I need to know whether this
>> fixup is okay to go cause I'll need to submit to Chrome OS then.
>
> Sure it is fine. The code is already there, we cannot change it.
ah true. Only now that I've noticed it's already in Linus tree. Thanks
anyway!
Tiago
next prev parent reply other threads:[~2016-03-29 17:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 20:02 [PATCH] dma-buf,drm,ion: Propagate error code from dma_buf_start_cpu_access() Chris Wilson
2016-03-19 10:09 ` [PATCH] dma-buf, drm, ion: " Daniel Vetter
2016-03-21 6:13 ` Sumit Semwal
2016-03-21 7:30 ` [PATCH] dma-buf: Update docs for SYNC ioctl Daniel Vetter
2016-03-21 7:35 ` Sumit Semwal
2016-03-21 7:40 ` Hans Verkuil
2016-03-21 7:50 ` Daniel Vetter
2016-03-21 7:51 ` Daniel Vetter
2016-03-21 7:53 ` Hans Verkuil
2016-03-21 12:26 ` David Herrmann
2016-03-21 17:14 ` Daniel Vetter
2016-03-23 11:30 ` David Herrmann
2016-03-23 11:56 ` Chris Wilson
2016-03-23 15:32 ` David Herrmann
2016-03-23 15:42 ` Chris Wilson
2016-03-28 19:42 ` Tiago Vignatti
2016-03-29 9:47 ` David Herrmann
2016-03-29 17:20 ` Tiago Vignatti [this message]
2016-03-21 13:16 ` Tiago Vignatti
2016-03-21 13:13 ` [PATCH] dma-buf,drm,ion: Propagate error code from dma_buf_start_cpu_access() Tiago Vignatti
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=56FAB954.2060408@intel.com \
--to=tiago.vignatti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=marcheu@chromium.org \
--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).