dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/atomic-helper: properly annotate functions in kerneldoc
Date: Tue, 25 Aug 2015 18:00:26 +0300	[thread overview]
Message-ID: <1698581.0W6RChyToG@avalon> (raw)
In-Reply-To: <1440512763-797-1-git-send-email-daniel.vetter@ffwll.ch>

Hi Daniel,

Thank you for the patch.

On Tuesday 25 August 2015 16:26:03 Daniel Vetter wrote:
> Without the () the markup and more important hyperlinking wont happen.
> 
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  drivers/gpu/drm/drm_atomic_helper.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_atomic_helper.c
> b/drivers/gpu/drm/drm_atomic_helper.c index bc9c94e4cbaa..904acf236f36
> 100644
> --- a/drivers/gpu/drm/drm_atomic_helper.c
> +++ b/drivers/gpu/drm/drm_atomic_helper.c
> @@ -42,14 +42,14 @@
>   * add their own additional internal state.
>   *
>   * This library also provides default implementations for the check
> callback in
> - * drm_atomic_helper_check and for the commit callback with
> - * drm_atomic_helper_commit. But the individual stages and callbacks are
> expose
> + * drm_atomic_helper_check() and for the commit callback with
> + * drm_atomic_helper_commit(). But the individual stages and callbacks are
> expose

While at it, could you fix the typo here with s/expose/exposed/ ?

Apart from that,

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

>   * to allow drivers to mix and match and e.g. use the plane helpers only
>   * together with a driver private modeset implementation.
>   *
>   * This library also provides implementations for all the legacy driver
> - * interfaces on top of the atomic interface. See
> drm_atomic_helper_set_config,
> - * drm_atomic_helper_disable_plane, drm_atomic_helper_disable_plane and the
> + * interfaces on top of the atomic interface. See
> drm_atomic_helper_set_config(),
> + * drm_atomic_helper_disable_plane(), drm_atomic_helper_disable_plane() and
> the
> * various functions to implement set_property callbacks. New drivers must
> not
> * implement these functions themselves but must use the provided helpers. */
> @@ -1078,7 +1078,7 @@ EXPORT_SYMBOL(drm_atomic_helper_commit);
>   * work item, which allows nice concurrent updates on disjoint sets of
> crtcs.
>   *
>   * 3. The software state is updated synchronously with
> - * drm_atomic_helper_swap_state. Doing this under the protection of all
> modeset
> + * drm_atomic_helper_swap_state(). Doing this under the protection of all
> modeset
>   * locks means concurrent callers never see inconsistent state. And doing
> this
>   * while it's guaranteed that no relevant async worker runs means that
> async
>   * workers do not need grab any locks. Actually they must not grab locks,
> for
> @@ -1351,7 +1351,7 @@
> EXPORT_SYMBOL(drm_atomic_helper_cleanup_planes); *
>   * 4. Actually commit the hardware state.
>   *
> - * 5. Call drm_atomic_helper_cleanup_planes with @state, which since step 3
> + * 5. Call drm_atomic_helper_cleanup_planes() with @state, which since
> step 3
>   * contains the old state. Also do any other cleanup required with that
> state.
>   */
>  void drm_atomic_helper_swap_state(struct drm_device *dev,

-- 
Regards,

Laurent Pinchart

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-25 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 14:26 [PATCH] drm/atomic-helper: properly annotate functions in kerneldoc Daniel Vetter
2015-08-25 15:00 ` Laurent Pinchart [this message]
2015-08-25 15:12   ` Daniel Vetter

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=1698581.0W6RChyToG@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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