dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chunming Zhou <david1.zhou@amd.com>
Cc: easy2remember.chk@googlemail.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: fix missing doc v2
Date: Wed, 17 Oct 2018 09:10:45 +0200	[thread overview]
Message-ID: <20181017071045.GH31561@phenom.ffwll.local> (raw)
In-Reply-To: <20181017070318.15483-1-david1.zhou@amd.com>

On Wed, Oct 17, 2018 at 03:03:18PM +0800, Chunming Zhou wrote:
> flags is new param for drm_syncob_find_fence, so need update doc, reproduce: make htmldocs
> 
> reported:
> htmldocs: drivers/gpu/drm/drm_syncobj.c:230: warning: Function parameter or member 'flags' not described in 'drm_syncobj_find_fence'
> 
> v2: rebased
> 
> Signed-off-by: Chunming Zhou <david1.zhou@amd.com>

Thanks, applied.
-Daniel

> ---
>  drivers/gpu/drm/drm_syncobj.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
> index 094513125153..e2c5b3ca4824 100644
> --- a/drivers/gpu/drm/drm_syncobj.c
> +++ b/drivers/gpu/drm/drm_syncobj.c
> @@ -214,6 +214,7 @@ static int drm_syncobj_assign_null_handle(struct drm_syncobj *syncobj)
>   * @file_private: drm file private pointer
>   * @handle: sync object handle to lookup.
>   * @point: timeline point
> + * @flags: DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT or not
>   * @fence: out parameter for the fence
>   *
>   * This is just a convenience function that combines drm_syncobj_find() and
> -- 
> 2.17.1
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2018-10-17  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  7:03 [PATCH] drm: fix missing doc v2 Chunming Zhou
2018-10-17  7:10 ` 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=20181017071045.GH31561@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=david1.zhou@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=easy2remember.chk@googlemail.com \
    /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