public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Sean Paul <sean@poorly.run>
Cc: Pekka Paalanen <pekka.paalanen@collabora.com>,
	Jani Nikula <jani.nikula@intel.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <seanpaul@chromium.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] drm: Fix kerneldoc warns in connector-related docs
Date: Wed, 7 Aug 2019 19:30:23 +0200	[thread overview]
Message-ID: <20190807173023.GA30025@ravnborg.org> (raw)
In-Reply-To: <20190807162808.119141-1-sean@poorly.run>

Hi Sean.

On Wed, Aug 07, 2019 at 12:28:04PM -0400, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
> 
> Fixes the following warnings:
> ../drivers/gpu/drm/drm_connector.c:989: WARNING: Unexpected indentation.
> ../drivers/gpu/drm/drm_connector.c:993: WARNING: Unexpected indentation.
> ../include/drm/drm_connector.h:544: WARNING: Inline interpreted text or phrase reference start-string without end-string.
> ../include/drm/drm_connector.h:544: WARNING: Inline interpreted text or phrase reference start-string without end-string.

Thanks, 4 less warnings..
> 
> Fixes: 1b27fbdde1df ("drm: Add drm_atomic_get_(old|new)_connector_for_encoder() helpers")
> Fixes: bb5a45d40d50 ("drm/hdcp: update content protection property with uevent")
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Pekka Paalanen <pekka.paalanen@collabora.com>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Sean Paul <seanpaul@chromium.org>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: Sean Paul <sean@poorly.run>
> Cc: David Airlie <airlied@linux.ie>
> Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
>  drivers/gpu/drm/drm_connector.c | 10 ++++++----
>  include/drm/drm_connector.h     |  4 ++--
>  2 files changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> index 354798bad576..4c766624b20d 100644
> --- a/drivers/gpu/drm/drm_connector.c
> +++ b/drivers/gpu/drm/drm_connector.c
> @@ -986,12 +986,14 @@ static const struct drm_prop_enum_list hdmi_colorspaces[] = {
>   *	- Kernel sends uevent with the connector id and property id through
>   *	  @drm_hdcp_update_content_protection, upon below kernel triggered
>   *	  scenarios:
> - *		DESIRED -> ENABLED	(authentication success)
> - *		ENABLED -> DESIRED	(termination of authentication)
> + *
> + *		- DESIRED -> ENABLED (authentication success)
> + *		- ENABLED -> DESIRED (termination of authentication)
>   *	- Please note no uevents for userspace triggered property state changes,
>   *	  which can't fail such as
> - *		DESIRED/ENABLED -> UNDESIRED
> - *		UNDESIRED -> DESIRED
> + *
> + *		- DESIRED/ENABLED -> UNDESIRED
> + *		- UNDESIRED -> DESIRED
>   *	- Userspace is responsible for polling the property or listen to uevents
>   *	  to determine when the value transitions from ENABLED to DESIRED.
>   *	  This signifies the link is no longer protected and userspace should
> diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
> index 0b9997e27689..e391f9c05f98 100644
> --- a/include/drm/drm_connector.h
> +++ b/include/drm/drm_connector.h
> @@ -543,8 +543,8 @@ struct drm_connector_state {
>  	 *
>  	 * This is also used in the atomic helpers to map encoders to their
>  	 * current and previous connectors, see
> -	 * &drm_atomic_get_old_connector_for_encoder() and
> -	 * &drm_atomic_get_new_connector_for_encoder().
> +	 * &drm_atomic_get_old_connector_for_encoder and
> +	 * &drm_atomic_get_new_connector_for_encoder.
Please fix this to use () for the functions and drop the "&".
This is what we use in drm kernel-doc for functions.
See for example function references in doc of writeback_job in the same file.

With this fixed:
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>

>  	 *
>  	 * NOTE: Atomic drivers must fill this out (either themselves or through
>  	 * helpers), for otherwise the GETCONNECTOR and GETENCODER IOCTLs will
> -- 
> Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-08-07 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 16:28 [PATCH] drm: Fix kerneldoc warns in connector-related docs Sean Paul
2019-08-07 17:30 ` Sam Ravnborg [this message]
2019-08-09 19:05   ` Sean Paul
2019-08-09 20:15     ` Sam Ravnborg
2019-08-09 20:29       ` Sean Paul
2019-08-09 21:06         ` Sam Ravnborg
2019-08-12 14:01           ` [PATCH v2] " Sean Paul

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=20190807173023.GA30025@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=pekka.paalanen@collabora.com \
    --cc=sean@poorly.run \
    --cc=seanpaul@chromium.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