All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: "Emilio López" <emilio.lopez@collabora.co.uk>
Cc: sumit.semwal@linaro.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-buf/sync_file: fix documentation error
Date: Mon, 19 Sep 2016 09:10:22 -0300	[thread overview]
Message-ID: <20160919121022.GH13282@joana> (raw)
In-Reply-To: <20160919042120.6280-1-emilio.lopez@collabora.co.uk>

Hi Emilio,

2016-09-19 Emilio López <emilio.lopez@collabora.co.uk>:

> The ioctl name and description on the documentation block don't
> match the ioctl being defined. This was probably overlooked while
> renaming the ioctls during the sync file destaging. This patch
> provides a more accurate description of what the ioctl actually does.
> 
> Signed-off-by: Emilio López <emilio.lopez@collabora.co.uk>
> ---
> 
> This is something I saw while refreshing my kselftest patches. Hopefully
> this patch describes the new ioctl well enough, let me know if you
> think it doesn't :)
> 
> Cheers,
> Emilio
> 
>  include/uapi/linux/sync_file.h | 13 +++++--------
>  1 file changed, 5 insertions(+), 8 deletions(-)
> 
> diff --git a/include/uapi/linux/sync_file.h b/include/uapi/linux/sync_file.h
> index 413303d..cdf8ec2 100644
> --- a/include/uapi/linux/sync_file.h
> +++ b/include/uapi/linux/sync_file.h
> @@ -85,15 +85,12 @@ struct sync_file_info {
>  #define SYNC_IOC_MERGE		_IOWR(SYNC_IOC_MAGIC, 3, struct sync_merge_data)
>  
>  /**
> - * DOC: SYNC_IOC_FENCE_INFO - get detailed information on a fence
> + * DOC: SYNC_IOC_FILE_INFO - get detailed information on a sync_file
>   *
> - * Takes a struct sync_file_info_data with extra space allocated for pt_info.
> - * Caller should write the size of the buffer into len.  On return, len is
> - * updated to reflect the total size of the sync_file_info_data including
> - * pt_info.
> - *
> - * pt_info is a buffer containing sync_pt_infos for every sync_pt in the fence.
> - * To iterate over the sync_pt_infos, use the sync_pt_info.len field.
> + * Takes a struct sync_file_info. If num_fences is 0, the field is updated
> + * with the actual number of fences. If num_fences is > 0, the system will
> + * use the pointer provided on sync_fence_info to return up to num_fences of
> + * struct sync_fence_info, with detailed fence information.
>   */

Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>

Gustavo

  reply	other threads:[~2016-09-19 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  4:21 [PATCH] dma-buf/sync_file: fix documentation error Emilio López
2016-09-19 12:10 ` Gustavo Padovan [this message]
2016-09-20 12:57   ` 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=20160919121022.GH13282@joana \
    --to=gustavo.padovan@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emilio.lopez@collabora.co.uk \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.