From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/4] dma-buf/reservation doc updates
Date: Thu, 31 Mar 2016 16:26:48 -0400 [thread overview]
Message-ID: <1459456012-16248-1-git-send-email-robdclark@gmail.com> (raw)
Some dma-buf headerdoc fixes (turns out dma-buf.h wasn't getting pulled
into doc build), add reservation headerdoc, and fixup a bit the section
in device-drivers.tmpl.
Rob Clark (4):
reservation: sprinkle some WARN_ON()s
dma-buf: headerdoc fixes
reservation: add headerdoc comments
doc: update/fixup dma-buf related DocBook
Documentation/DocBook/device-drivers.tmpl | 36 ++++++++++++--
drivers/dma-buf/reservation.c | 78 +++++++++++++++++++++++++++++--
include/linux/dma-buf.h | 13 ++++--
include/linux/reservation.h | 53 +++++++++++++++++++++
4 files changed, 169 insertions(+), 11 deletions(-)
--
2.5.5
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-03-31 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:26 Rob Clark [this message]
2016-03-31 20:26 ` [PATCH 1/4] reservation: sprinkle some WARN_ON()s Rob Clark
2016-04-01 8:48 ` Lucas Stach
2016-04-01 14:50 ` Rob Clark
2016-04-01 14:02 ` Christian König
2016-03-31 20:26 ` [PATCH 2/4] dma-buf: headerdoc fixes Rob Clark
2016-03-31 20:26 ` [PATCH 3/4] reservation: add headerdoc comments Rob Clark
2016-03-31 20:26 ` [PATCH 4/4] doc: update/fixup dma-buf related DocBook Rob Clark
2016-04-01 14:07 ` [PATCH 0/4] dma-buf/reservation doc updates Alex Deucher
2016-04-01 15:20 ` Sumit Semwal
2016-06-04 12:21 ` Daniel Vetter
2016-06-05 11:17 ` Sumit Semwal
2016-06-05 17:18 ` Daniel Vetter
2016-06-06 4:41 ` Sumit Semwal
[not found] <Message-Id: <1459456012-16248-2-git-send-email-robdclark@gmail.com>
2016-04-08 0:52 ` [PATCH] reservation: sprinkle some WARN_ON()s Rob Clark
2016-06-04 12:52 ` Daniel Vetter
2016-06-04 15:47 ` Rob Clark
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=1459456012-16248-1-git-send-email-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=dri-devel@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