From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
linux-doc@vger.kernel.org, Sumit Semwal <sumit.semwal@linaro.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/5] dma-buf: Extract dma-buf.rst
Date: Sun, 11 Dec 2016 13:41:40 -0700 [thread overview]
Message-ID: <20161211134140.3ecb78ab@lwn.net> (raw)
In-Reply-To: <20161209185309.1682-2-daniel.vetter@ffwll.ch>
On Fri, 9 Dec 2016 19:53:05 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Just prep work to polish and consolidate all the dma-buf related
> documenation.
>
> Unfortunately I didn't discover a way to both integrate this new file
> into the overall toc while keeping it at the current place. Work
> around that by moving it into the overall driver-api/index.rst.
OK, I've applied this, with one change:
> diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h
> index d51a7d23c358..c683c4e908d2 100644
> --- a/include/linux/dma-fence.h
> +++ b/include/linux/dma-fence.h
> @@ -163,7 +163,6 @@ struct dma_fence_cb {
> * destruction of the fence. Can be called from irq context.
> * If pointer is set to NULL, kfree will get called instead.
> */
> -
> struct dma_fence_ops {
> const char * (*get_driver_name)(struct dma_fence *fence);
> const char * (*get_timeline_name)(struct dma_fence *fence);
This hunk didn't apply to my tree, but I figured that, under duress, we
could probably manage to do without it for now...:)
jon
next prev parent reply other threads:[~2016-12-11 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 18:53 [PATCH 0/5] sphinxification for dma-buf docs Daniel Vetter
2016-12-09 18:53 ` [PATCH 1/5] dma-buf: Extract dma-buf.rst Daniel Vetter
2016-12-11 20:41 ` Jonathan Corbet [this message]
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 19:15 ` ✓ Fi.CI.BAT: success for sphinxification for dma-buf docs Patchwork
2016-12-09 21:15 ` [PATCH 0/5] " 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
2016-12-09 22:23 ` ✓ Fi.CI.BAT: success for sphinxification for dma-buf docs (rev2) Patchwork
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=20161211134140.3ecb78ab@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.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).