From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: [PATCH 0/5] sphinxification for dma-buf docs
Date: Fri, 9 Dec 2016 19:53:04 +0100 [thread overview]
Message-ID: <20161209185309.1682-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
Not yet everything in this area, I still want to sprinkle nice docs around all
the fence code. Especially some text to explain implicit vs. explicit fencing
and how it's all supposed to work.
But just cleanup in the dma-buf part was quite a bit of work, and I'd like to
get feedback on that before moving on.
Cheers, Daniel
Daniel Vetter (5):
dma-buf: Extract dma-buf.rst
dma-buf: Update kerneldoc for sync_file_create
dma-buf: Reorganize device dma access docs
dma-buf: Update cpu access documentation
dma-buf: Final bits of doc polish
Documentation/dma-buf-sharing.txt | 482 ----------------------------
Documentation/driver-api/dma-buf.rst | 165 ++++++++++
Documentation/driver-api/index.rst | 1 +
Documentation/driver-api/infrastructure.rst | 70 ----
drivers/dma-buf/dma-buf.c | 207 +++++++++++-
drivers/dma-buf/sync_file.c | 15 +-
include/linux/dma-buf.h | 224 +++++++++++--
include/linux/dma-fence.h | 1 -
8 files changed, 565 insertions(+), 600 deletions(-)
delete mode 100644 Documentation/dma-buf-sharing.txt
create mode 100644 Documentation/driver-api/dma-buf.rst
--
2.10.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-12-09 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 18:53 Daniel Vetter [this message]
2016-12-09 18:53 ` [PATCH 1/5] dma-buf: Extract dma-buf.rst Daniel Vetter
2016-12-11 20:41 ` Jonathan Corbet
2016-12-12 12:30 ` Gustavo Padovan
2016-12-09 18:53 ` [PATCH 2/5] dma-buf: Update kerneldoc for sync_file_create Daniel Vetter
2016-12-12 12:34 ` [Intel-gfx] " Gustavo Padovan
2016-12-09 18:53 ` [PATCH 3/5] dma-buf: Reorganize device dma access docs Daniel Vetter
2016-12-09 18:53 ` [PATCH 4/5] dma-buf: Update cpu access documentation Daniel Vetter
2016-12-09 18:53 ` [PATCH 5/5] dma-buf: Final bits of doc polish Daniel Vetter
2016-12-09 21:50 ` [PATCH] " Daniel Vetter
2016-12-09 21:15 ` [PATCH 0/5] sphinxification for dma-buf docs Jonathan Corbet
2016-12-11 12:12 ` Sumit Semwal
2016-12-11 12:35 ` Daniel Vetter
2016-12-11 15:11 ` Jonathan Corbet
2016-12-11 17:35 ` Daniel Vetter
2016-12-11 19:44 ` Jonathan Corbet
2016-12-13 12:34 ` 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=20161209185309.1682-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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