All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: James Jones <jajones@nvidia.com>,
	Daniel Stone <daniels@collabora.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] doc: gpu: Add document describing buffer exchange
Date: Thu, 3 Aug 2023 16:46:25 +0100	[thread overview]
Message-ID: <CAPj87rPaGtRirzB3-Gk+3i-=xrdA4O9LR6dV36smCgJH9JU3EA@mail.gmail.com> (raw)
In-Reply-To: <YYo7wHBACwgwy3W+@phenom.ffwll.local>

On Tue, 9 Nov 2021 at 09:13, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, Nov 08, 2021 at 04:18:22PM -0800, James Jones wrote:
> > On 9/6/21 5:28 AM, Simon Ser wrote:
> > > > Since there's a lot of confusion around this, document both the rules
> > > > and the best practice around negotiating, allocating, importing, and
> > > > using buffers when crossing context/process/device/subsystem boundaries.
> > > >
> > > > This ties up all of dmabuf, formats and modifiers, and their usage.
> > > >
> > > > Signed-off-by: Daniel Stone <daniels@collabora.com>
> > >
> > > Thanks a lot for this write-up! This looks very good to me, a few comments
> > > below.
> >
> > Agreed, it would be awesome if this were merged somewhere. IMHO, a lot of
> > the non-trivial/typo suggestions below could be taken care of as follow-on
> > patches, as the content here is better in than out, even if it could be
> > clarified a bit.
>
> Seconded on just landing this without trying to perfect it first, because
> I was just looking for it and didn't find it anywhere :-/

Swing and a miss ...

I've just sent out v2 with - AFAICT - all the changes from all

Cheers,
Daniel

  parent reply	other threads:[~2023-08-03 15:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 12:27 [PATCH] doc: gpu: Add document describing buffer exchange Daniel Stone
2021-09-06 12:28 ` Simon Ser
2021-11-09  0:18   ` James Jones
2021-11-09  9:13     ` Daniel Vetter
2021-11-09  9:22       ` Simon Ser
2023-08-03 15:46       ` Daniel Stone [this message]
2023-08-03 15:46         ` Daniel Stone
2021-09-06 17:13 ` Robert Beckett
2021-09-08  9:34 ` Pekka Paalanen
2021-09-08  9:44   ` Simon Ser
2021-11-09  0:21     ` James Jones
2021-11-09  9:12       ` Daniel Vetter
2021-09-08 18:16 ` Daniel Vetter
2023-08-03 15:47 ` [PATCH v2 0/2] doc: uapi: Document dma-buf interop design & semantics Daniel Stone
2023-08-03 19:47   ` James Jones
2023-08-03 20:30   ` Sebastian Wick
2023-08-03 20:30     ` Sebastian Wick
2023-08-29 13:30   ` [Linaro-mm-sig] " Christian König
2023-08-03 15:47 ` [PATCH v2 1/2] doc: dma-buf: Rewrite intro section a little Daniel Stone
2023-08-03 15:47 ` [PATCH v2 2/2] doc: uapi: Add document describing dma-buf semantics Daniel Stone
2023-08-18 15:37   ` [v2,2/2] " suijingfeng
2023-08-21 13:33   ` [PATCH v2 2/2] " Daniel Vetter
2023-08-21 17:17     ` Simon Ser

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='CAPj87rPaGtRirzB3-Gk+3i-=xrdA4O9LR6dV36smCgJH9JU3EA@mail.gmail.com' \
    --to=daniel@fooishbar.org \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jajones@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.