From: Daniel Stone <daniels@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org
Subject: [PATCH v2 0/2] doc: uapi: Document dma-buf interop design & semantics
Date: Thu, 3 Aug 2023 16:47:27 +0100 [thread overview]
Message-ID: <20230803154908.105124-2-daniels@collabora.com> (raw)
In-Reply-To: <20210905122742.86029-1-daniels@collabora.com>
Hi all,
This is v2 to the linked patch series; thanks to everyone for reviewing
the initial version. I've moved this out of a pure DRM scope and into
the general userspace-API design section. Hopefully it helps others and
answers a bunch of questions.
I think it'd be great to have input/links/reflections from other
subsystems as well here.
Cheers,
Daniel
next prev parent reply other threads:[~2023-08-03 15:49 UTC|newest]
Thread overview: 22+ 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
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 ` Daniel Stone [this message]
2023-08-03 19:47 ` [PATCH v2 0/2] doc: uapi: Document dma-buf interop design & semantics James Jones
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=20230803154908.105124-2-daniels@collabora.com \
--to=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.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