From: Daniel Vetter <daniel@ffwll.ch>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
Gustavo Padovan <gustavo@padovan.org>,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf/sw_sync: fix document of sw_sync_create_fence_data
Date: Mon, 15 Jan 2018 10:47:19 +0100 [thread overview]
Message-ID: <20180115094719.GL13066@phenom.ffwll.local> (raw)
In-Reply-To: <1515988079-8677-1-git-send-email-shawn.guo@linaro.org>
On Mon, Jan 15, 2018 at 11:47:59AM +0800, Shawn Guo wrote:
> The structure should really be sw_sync_create_fence_data rather than
> sw_sync_ioctl_create_fence which is the function name.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Applied, thanks for your patch.
-Daniel
> ---
> drivers/dma-buf/sw_sync.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c
> index 24f83f9eeaed..7779bdbd18d1 100644
> --- a/drivers/dma-buf/sw_sync.c
> +++ b/drivers/dma-buf/sw_sync.c
> @@ -43,14 +43,14 @@
> * timelines.
> *
> * Fences can be created with SW_SYNC_IOC_CREATE_FENCE ioctl with struct
> - * sw_sync_ioctl_create_fence as parameter.
> + * sw_sync_create_fence_data as parameter.
> *
> * To increment the timeline counter, SW_SYNC_IOC_INC ioctl should be used
> * with the increment as u32. This will update the last signaled value
> * from the timeline and signal any fence that has a seqno smaller or equal
> * to it.
> *
> - * struct sw_sync_ioctl_create_fence
> + * struct sw_sync_create_fence_data
> * @value: the seqno to initialise the fence with
> * @name: the name of the new sync point
> * @fence: return the fd of the new sync_file with the created fence
> --
> 1.9.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2018-01-15 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 3:47 [PATCH] dma-buf/sw_sync: fix document of sw_sync_create_fence_data Shawn Guo
2018-01-15 9:47 ` Daniel Vetter [this message]
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=20180115094719.GL13066@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-media@vger.kernel.org \
--cc=shawn.guo@linaro.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